Skip to content

add links to native code coverage example and backend cove… #1788

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Sep 20, 2019
Merged

add links to native code coverage example and backend cove… #1788

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
dde282e
WIP: add links to native code coverage example and backend coverage
bahmutov Jun 18, 2019
2f535a7
Merge branch 'develop' into add-native-coverage-link
jennifer-shehane Jul 9, 2019
96f181c
Merge branch 'develop' into add-native-coverage-link
bahmutov Sep 20, 2019
0842bb2
Use "back end" term
bahmutov Sep 20, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions source/guides/tooling/code-coverage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -423,6 +423,12 @@ From now on, the front end code coverage collected during end-to-end tests will

You can explore the above combined full stack coverage report at the {% url 'coveralls.io/github/cypress-io/cypress-example-realworld' https://coveralls.io/github/cypress-io/cypress-example-realworld %} dashboard.

# Future work

We are currently exploring two additional features for code coverage during end-to-end tests. First, we would like to avoid "manual" instrumentation step using Istanbul.js library and instead capture the native code coverage that can be collected by the Chrome browser's V8 engine. You can find a proof-of-concept example in {% url bahmutov/cypress-native-chrome-code-coverage-example https://github.com/bahmutov/cypress-native-chrome-code-coverage-example %} repository.

Second, we would like to capture the code coverage from *the locally running back end server* that is serving the front end web application and handles the API requests from the web application under test. We believe that E2E tests with additional {% url "API tests" https://www.cypress.io/blog/2017/11/07/add-gui-to-your-e2e-api-tests/ %} that Cypress can perform can effectively cover a lot of back end code.

# Examples

You can find full examples showing different code coverage setups in the following repositories:
Expand Down