-
Notifications
You must be signed in to change notification settings - Fork 3
configure modules
Michal Sporna edited this page Jul 29, 2018
·
2 revisions
There is a Modules link in top right part of the screen.
Modules are containers for source files detected and uploaded automatically by instrument_client. Modules are required to start a new test session.
Human readable module names are more user friendly when viewing test report than looking at source files (but those are also in the report). Besides, you can gather coverage only for specific modules and skip others. * you want to test Settings page * you get a bunch of source files from instrument_client * create module named Settings * assign related source files to that module * start new session and select Settings module only * go your testing * LAVA tool gathers test coverage only for sources related to selected modules, skips other files * finish testing * fou know how much of Settings your testing covered- use instrument_client to upload sources to LAVA (see 'get-the-coverage' page-it's in this wiki)
- go to dashboard
- click on modules link
- left pane is a list of modules - probably empty for now, right pane is a list of source files detected
- create modules by clicking on a green button and specify unique module name
- once it's created, it will appear in the left pane
- select sources you want to assign to that module
- select module
- click on assign button
- if everything goes well-files will dissapear from right pane and appear in the left pane, under chosen module.
- you can now select this module when creating a new test session.
- when you remove module with files in it, files will get unassigned
- you can unassign file anytime
- if module has some file, then you upload sources again (next build) and source file is not there anymore, it will automatically be removed from module
- if you has source file in module and start test session with it, then remove module or unassign file - archived session will still show that file in module or module - removing and unassigning does not affect archived test sessions.
- 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