-
Notifications
You must be signed in to change notification settings - Fork 3
How to interpret covered lines report
msporna edited this page Jan 8, 2019
·
3 revisions
Coverage report contains list of source files and code lines that were triggered by your testing activity. Each file can be clicked and a popup showing source file with indication which line was executed and which missed:
breakdown from the top:
- lines executed: 314,315,316,317
- lines missed: 318
- lines executed: 319,320
- 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