RapiCover

•Before running a coverage test using RapiCover, all other code coverage tools must be disabled.

•MxSuite 3.41.8 or higher is required to use RapiCover Express.

In MxSuite 3.42 and higher, RapiCover is installed by the MxSuite installer.

MxSuite 3.41 and earlier

There are two methods for enabling code coverage of a VMC:

From Mx‑VDev

Using the Transform Property

In MxTransIt, click the VMC Transform to select it and display its Properties Box. Set the Enable RapiCover coverage property to True. The coverage status (enabled/disabled) is set each time the MxV project is loaded or the Harness is connected. You can override the status in MxVDev. For a Module You can enable and disable coverage and analysis within a particular module utilizing the pragma statements described in the RVS Annotations Reference. The key directives that are used are the enable_instrumentation and disable_instrumentation pragmas as described in section 7.1. Inserting a disable_instrumentation pragma in the source will disable RapiCover instrumentation until such time as an enable_instrumentation pragma is encountered. By surrounding function calls with a disable_instrumentation/enable_instrumentation pragma pair, users may selectively exclude specific functions from instrumentation. In addition, by placing an disable_instrumentation pragma at the beginning of a source code module, entire modules may be excluded from instrumentation. For more information, and other directives available, see the C:\ProgramData\Danlaw\MxSuite\RapiCoverIntegration\2.0\doc folder.

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
 
<project-folder>\SUT\MxVTarget\rvs_MxVTarget\maps.
 
A file called tracefiles.txt that lists all the map files is also produced.

•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:

•RapiCover_(AutoHarness)VMC.log

•RapiCover_(MxV)CruiseControlAlg.log

The log file is in this folder:

C:\Users\<your-username>\AppData\Roaming\MicroMax\Logs\

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 mxsupport@danlawinc.com