-
Notifications
You must be signed in to change notification settings - Fork 3
How it works
Probes are inserted into code files of software under test that QA wants to get test coverage from. Probes are inserted automatically by instrument_client python script. The script talks to instrument_server that typically runs on port 5000. The client detects all source files within specified in config source root, injects probes and uploads list of them to the server.
After that, the tool has a list of sources along with contents and executable lines.
The probes are simple lines of code that, simply put, call server's api with details like line unique ID or index number. So when probe code is executed (hopefully via your testing activity), it sends info to server and server knows which line was just executed.
Knowing how many lines are there in overall, it can be determined what percentage of executable lines, were triggered lines. This is test coverage.
- 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