https://cypress.io logo
Join DiscordCommunities
Powered by
# e2e-testing
  • b
    In my opinion, Early on in a project, you want to build components in isolation. If you use TDD, you can clearly see what part is covered and avoid creating components that won't be useful. But this coverage is local and does not say anything about the way your app works. It tells you how your TESTS work in isolation. It gives you info about the components but not the app itself.
  • b
    You could have all components working and 100% tested and have an app that is failing miserably because all component are used improperly
  • b
    So I like to know what part of my code is tested in integration and what is tested in isolation
  • b
    This is really an opinion and I know it is not of everyone
  • b
    Unit testing => a dev/refactor tool
  • b
    E2E testing => a safety net
  • b
    I should post about this vision
  • c
    very true but the intention of that why is different, the intention or purpose of a coverage is to know how much of your code is tested and how much is pending, whether it is in isolated or integrated shouldnt matter, isnt it? If i have an application with 5 components and used in 6 places to be tested for integration then when i look for coverage i wonder if a dev would/should think about is the coverage from isolated or integration environment True these are opinionated topics
  • b
    If I want to know if my app is safe from regressions I will need more e2e code coverage
  • c
    one final question, and after this I think i have successfully setup a cypress testing for my teams huge react app including component testing, e2e testing, unit testing, snapshot testing, coverage
  • b
    If I am about to refactor a part of my code I would really hope that component tests about this fully cover that part
  • c
    When I run e2e testing it says found only unit tet code coverage, i wonder why, it doesnt show coverage of code under e2e
  • c
    "If I want to know if my app is safe from regressions I will need more e2e code coverage" Very fair point. Also, i didn mean I would be writing tests only for coverage purpose, I would be writing enough tests based on the test-cases that are required rather than just coverage purpose, coverage is just one of the tool i would be using to get a decent idea
  • c
    that file containing e2e testing has no unit tests or imports at all.
  • b
    did you load the support from cypress/code-coverage ?
  • c
    this is my support file
  • b
  • c
    I see it fails if windowCoverageObjects.length but succeeds window.__coverage__.length
  • b
    To track it down I would put a debugger statement inside your node_modules
  • c
    thanks a bunch
  • c
    It looks it is saying the app is not instrumented, I have followed https://docs.cypress.io/guides/tooling/code-coverage#Using-code-transpilation-pipeline instead of nyc, will check why it is not instrumented
  • h
    Can someone get me some article which compares cypress and selenium. It's advantages, disadvantages, features etc
  • c
    Sorry but I tried everything that is listed to make sure my react app is instrumented using https://docs.cypress.io/guides/tooling/code-coverage#Using-code-transpilation-pipeline and not using nyc. Step1: Added istanbul to babelrc so it looks like below now Step 2: Cypress open step 3: When running a e2e test using visit() check for window.__coverage__ under App: as specificed here https://github.com/cypress-io/code-coverage#instrument-your-application But i dont see window.__coverage__ What am i missing?
  • c
    my .nycrc file. I have tried other combinations too but this is my current one.
  • c
    my .babelrc file
  • c
    my support file cypress/support/index.js
  • c
    .babelrc
  • c
    my cypress/plugin/index.js
  • c
    The issue is e2e testing coverage does not take place, I get a log msg saying only found unit code coverage
  • c
    This log too ⚠️ Could not find any coverage information in your application by looking at the window coverage object. Did you forget to instrument your application? See code-coverage#instrument-your-application [@cypress/code-coverage]
1...789...192Latest