Effective Release 220.127.116.11730
In MxTransIt, select the S-function Transform and set the Coverage Information properties:
•To enable coverage, set the first property to True.
•To generate a cumulative report, set Generate Cumulative HTML Report for all scenarios run to True. The report is updated as each scenario completes.
•To generate separate reports for each scenario, set Generate HTML Report On Scenario Completion to True.
Access the Coverage Settings dialog. The settings must be set in the harnessed model. If you specify the settings in the original model, they are copied when it is harnessed.
Coverage data is saved based upon the parameters set in the harnessed model. (The original model may have coverage disabled while the harnessed model may not). Note that these settings control the data that is saved (and therefore the data that is presented in the HTML reports). The settings on the Results and Reporting tabs are controlled by MxVDev.
In addition, model coverage options on the Options tab are in effect:
•The “Enable Coverage” option saves the coverage and test data that is later loadable by the Matlab cvload function. With the exception of the last item, each test in the coverage data cell array corresponds to a module reset point. The first item covers from model start to the first module reset in the Scenario. The second value corresponds to the coverage between the first module reset point, etc., with the second to last value corresponding to the coverage between the last module reset (or Scenario start if the scenario does not contain any module reset signals) and the Scenario end. The last item is the coverage totals of the entire Scenario.
•HTML reports for single Scenarios contain the test data for each test run that was saved for the Scenario. These are the coverage data broken down, Test 1 corresponds to the Scenario start to the first module reset, Test 2 corresponds to the data between the first and second module reset, etc. The final test (listed as “Test n” in the summary but labeled “Totals” in the details) contains the full totals for the scenario.
•HTML reports with diffs for single Scenarios contain the same results as above, however between each test is a difference in coverage report. Test 1 corresponds to the coverage from the start to first reset, Test 3 corresponds to the coverage between the first reset and second reset and Test 2 corresponds to the difference between those two tests. Test 5 corresponds to the coverage between the second reset and third reset, and Test 4 corresponds to the differences in coverage between Tests 5 and 3, etc. Again, the final test is the Totals for the Scenario.
•HTML reports for cumulative Scenario runs are the same as above, however each test in the report corresponds to only the final Scenario results in the order that the Scenarios are run. For example, if Scenarios A, B, and C are run in that order, the final report corresponds to Test 1 being the total coverage for Scenario A, Test 2 being the total coverage for Scenario B, Test 3 being the total coverage for Scenario C, and Test 4 Totals being the total coverage for all Scenarios. The difference reports work the same way, Test 1 corresponds to Scenario A, Test 2 corresponds to the differences between B and A, Test 3 corresponds to Scenario B, Test 4 corresponds to the differences between Scenarios C and B, Test 5 corresponds to Scenario C and Test 6 (Totals) corresponds to the cumulative coverage.
Any additional advanced coverage examination, manipulation, or reporting (for example, broader difference reports, or coverage intersection analysis) can be performed by loading the MxVDev harnessed model that generated the coverage data in MATLAB, and calling cvload to load the coverage data files that were generated during the Scenario run. See the Simulink Verification and Validation documentation for more information.
•For coverage to be saved, BOTH the “Enable Coverage” property must be true *and* the “Coverage for this model” in the GUI above must be checked. The data saved is the data generated by the settings above.
•The Coverage reports are stored in the "Coverage" subfolder of the model folder.
The MxSuite does not activate coverage for referenced models nor any of the options of what metrics are saved, this is a manual step. MxSuite only changes the overall points at which coverage data is saved. To activate coverage for submodels, perform the following steps:
1.Edit the ORIGINAL top level model. Note that it is important to do this in the original model, because on an MxVDev reharness, these settings revert back to the original if they are changed in the MxVDev model.
2.In the Coverage Settings panel, ensure that "Coverage for referenced models" is checked. You can exclude/include sub models as necessary using the Select Models button.