Skip to content

Instrumenting code on every iteration (CI)

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

If you wish to get coverage report for each build, on each new merge along with running your tests, then you need to remember couple of things:

  1. newly cloned code must be instrumented again
  2. test coverage session created after that must have a totally new build number assigned.

explanation:

If you instrument a new code, then source file lines will have new guid numbers that are different from what's already stored in DB. If you create a test coverage session with existing build number, you'll get a false build coverage report containing more than 1 set of stats for each file:

That's because coverage session that already exist for build has stats for some file and new session with the same build also, but with different line GUIDs. Normally when generating build report, duplicated line guids are ignored and coverage for file across all builds is shown. In this case, false coverage for file is shown because there aren't any duplicates but new line guids coming from new instrumentation.

To avoid that (build coverage >100%):

simply remember 2 steps from above.

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