Skip to content

Getting coverage for build (multiple coverage sessions consolidated)

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

Test coverage sessions have a build and tag set. Build number is unique within tag and a consolidated report for all sessions related to a build can be generated.

There is a Build Summary located on the dashboard presenting stats for the latest build. It has:

  • coverage goal - you can set a minimum coverage goal (60% by default). If build coverage is less than that, then the summary area will be orange (or warning color) and green otherwise.
  • current coverage - current coverage calculated from all test coverage sessions for the build
  • build number - build number for which coverage is shown. It is the latest by default but can be switched.
  • related tag - tag owning the build. Each build has a parent tag and builds are unique within tags.

A report can be generated for specific build by either of those:

  • using a 'Generate Report' link next to build number
  • navigating to [LAVA host]/report/build/[BUILD NUMBER]/tag/[TAG NAME]

Why is it useful? There might be multiple coverage sessions for 1 build, each calculating coverage for different sources, triggered by different tests. Build coverage report consolidates them all into one general report.

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