Skip to content

Coverage report explained

Jump to bottom
msporna edited this page Jan 7, 2019 · 3 revisions

Here is an explanation what the coverage report consists of:

You can also see which exact lines of instrumented files were executed. To do such, look for a file you want to see under 'Coverage by file' and click on it. You will get a popup:

Scroll the code and look for lines highlighted in green. Each executed line sits in some web app's function, so by knowing which line was executed, you get exact function name triggered by your tests. Code lines that were missed during your testing are highlighted in yellow.

The last section of the report is timeline table showing all sources and executed line numbers one by one. The sources in that table are sorted ascending by execution time. You can use this functionality to for instance check if app flow triggered by your testing is as expected or to reproduce some issue.

Table of Contents

  1. How it works
  2. Initial setup
  3. Setup for Unity game
  4. Setup for Android app
  5. Setup for javascript
  6. Setup for Angular app
  7. GETTING THE COVERAGE
  8. Getting coverage for build (multiple coverage sessions consolidated
  9. Setup modules
  10. Managing tags
  11. Managing users
  12. Create and End test session automatically (CI)
  13. Instrumenting code on every iteration
  14. Coverage report explained
  15. Accessing latest report
  16. How to interpret covered lines report
  17. Config explained
  18. Settings
  19. Send custom values along with line statistics
  20. Examples
  21. Extended-CI-use-case
  22. Troubleshooting
Clone this wiki locally