Generating Additional Code Coverage Information During Build |
VIRTUAL MACHINE |
 |
|
Generating Additional Code Coverage Information During Build |
VIRTUAL MACHINE |
|
Trail: PROIV Documentation > Developer > PROIV Developer > Code Coverage > Generating additional code coverage information during build
A pre-requisite of using code coverage is that the Virtual Machine needs additional (symbolic) information about how logic source code maps to the logic instructions it executes. Code coverage is recorded or captured as low-level instructions are executed but users need to see code coverage at the logic source level. This additional information is generated as functions build. Code coverage captured in the absence of this additional information is (effectively) empty.
WARNING: turning on the generation of this additional code coverage information during the build stage could lead to a leaking of intellectual property. Please be aware of the dangers and the recommended practises to mitigate them before you begin.
By default the generation of the additional code coverage information during a build is disabled. It can be enabled via the PROIV Dashboard. The functions of interest for code coverage will need building again either individually or via bulk-build.
It is important to distinguish between the two switches for code coverage. There is one to enable the generation of the additional code coverage information during builds. This does not record or capture code coverage data. There is a separate switch to enable the capturing of code coverage data. Enabling code coverage capture implicitly enables the generation of the additional code coverage information as it is nonsensical to capture without generating. Capturing can also be enabled programmatically but this will fail with an error if the generation of the additional code information is disabled. Again because it is nonsensical to do one without the other and implies a misconfiguration.
Once the generation of additional code coverage information has been enabled and the functions of interest have been built again then it is time to start capturing code coverage data.
Topic ID: 700087