-
Notifications
You must be signed in to change notification settings - Fork 3
Updating LAVA test coverage
msporna edited this page Jan 7, 2019
·
2 revisions
- clone latest code
- copy your existing database to new version/server folder
- instrument your code (fresh)
- when creating a coverage session, remember to use a new build number (different from the last one) . The reason for this is explained in more detail here: https://github.com/msporna/LAVA-test-coverage/wiki/Instrumenting-code-on-every-iteration-(CI)
- How it works
- Initial setup
- Setup for Unity game
- Setup for Android app
- Setup for javascript
- Setup for Angular app
- GETTING THE COVERAGE
- Getting coverage for build (multiple coverage sessions consolidated
- Setup modules
- Managing tags
- Managing users
- Create and End test session automatically (CI)
- Instrumenting code on every iteration
- Coverage report explained
- Accessing latest report
- How to interpret covered lines report
- Config explained
- Settings
- Send custom values along with line statistics
- Examples
- Extended-CI-use-case
- Troubleshooting