First, your project's source files are injected with probes that are supposed to report usage back to Lava's server running in your local environment.
Execute your test cases as you always do - either manually or automatically. It does not matter how you interact with the product, what matters is which parts you interact with.
When the testing is done, a clean and detailed coverage report is available. After you identify areas of code not covered by your tests, you can update test cases to improve.
Coverage for Unity3D,Android and javascript happens on the fly as you are performing your functionl testing.
Get report for build consisting of source files and lines triggered by your testing and execution timeline showing sources sorted by execution order ascending. Reports are saved to drive in html format.
Assign build number and tag name to each coverage session to relate to current version of software being tested.
Modules functionality enables you to gather coverage only for selected source files (or for all)
Create test sessions, configure modules and view coverage reports in a simple yet functional web dashboard.
Setup process is easy and automated- after setting a couple of config entries, a Python script does all of the heavy lifting for you!
There are 3 examples showcasing usage of the tool from A to Z:
There is a web browser based game called LAVA_SIMULATOR taking you, the player, through the setup process of Lava Test Coverage and getting your first test coverage report in a Linux-like environment. Learn by playing in your browser!
