RapiCover Express for MxSuite provides code coverage analysis for MxVMC code. It is fully integrated with the MxSuite, however it is separately installed. It uses 4 license tokens.
For information on using RapiCover, see RapiCoverExpressForMxSuite.pdf. By default, this file is installed in the C:\ProgramData\Danlaw\MxSuite\RapiCoverIntegration\1.1\doc folder.
•Before running a coverage test using RapiCover, all other code coverage tools must be disabled.
•MxSuite 22.214.171.124698 or higher is required to use RapiCover Express.
•Java Runtime Environment 8 or higher (32-bit version) is required to run the RapiCover Integration installer. If you don't already have it, you can download it here:
1.Download the RapiCover installer from this website:
2.Run the RapiCover for MxSuite Installer. For example:
There are two methods for enabling code coverage of a VMC:
To produce a Code Coverage report for the first time, use this procedure:
1.Be sure RapiCover coverage is enabled.
The build must complete without errors. Check the Notifications box.
2.Run the test.
3.Select Transforms->VMC->View RapiCover report.
•When a test is run on an instrumented project, the coverage map files are written to .txt files into a folder such as
•When View RapiCover report is selected from the menu, the covparser program processes all the map files listed and creates an rvd file. Note: The map (.txt) files are deleted at this point.
•The Viewer displays the processed data from the rvd file. Optionally, the user can Save As.
•The only time the rvd is reset is when a rebuild is performed or a reset command is selected.
•You can also open the RapiCover Viewer by selecting Tools->RapiCover Coverage Viewer from the MxVDev main menu. This is useful for viewing previously saved rvd files.
The RVD file stores accumulated coverage stats for a particular build of the instrumented source code of the System Under Test (SUT). Stats accumulated on a particular build of the SUT are not valid for subsequent builds of the SUT (because in all likelihood the source code will have changed). Coverage measurements ‘for score’ have to be gathered on a single particular build of the of the SUT (typically by running all Scenarios, in the context of a Regression Test run).
In view of the above:
•Anytime the SUT is rebuilt for coverage, accumulated coverage stats in the RVD file are purged.
•To keep a copy of coverage stats for a particular version of the SUT, perform a File->Save As in the Coverage Viewer (before rebuilding the SUT).
In case of problems, refer to the RapiCover log file. The RapiCover log file is Transform specific and therefore includes the full Transform name with parenthesis separating parts of the "harness path." For example:
The log file is in this folder:
To access log files, select Help->View Log Files from the MxVDev main menu.
It may also be useful to examine the build log.
Please attach the log files when requesting support. Send all files and support requests to email@example.com