| Simulink® Verification and Validation™ | ![]() |
| On this page… |
|---|
If you enable the Generate HTML report option on the Coverage Settings dialog box (see Report Tab), the Simulink® Verification and Validation™ software creates a model coverage report at the end of a simulation. When recording coverage for multiple models in a hierarchy, the report displays a summary of each model's coverage results. Click the name of a model to view the coverage report for that model.

Otherwise, the Simulink Verification and Validation software displays the coverage report for a single model. The model coverage report contains several parts, each of which is described in the sections that follow.
For an understanding of model coverage reports for Stateflow® charts and their objects, see Understanding Model Coverage for Stateflow® Charts in the Stateflow documentation.
The coverage summary section has two subsections: Tests and Summary.

The Tests section lists the simulation start and stop time of each test case and any setup commands that preceded the simulation. The heading for each test case includes the test case label, for example "Test throttle," specified using the cvtest command.
The Summary section summarizes the results for each subsystem. Clicking the name of the subsystem takes you to a detailed report for that subsystem.
The Details section reports the model coverage results in detail.

The Details section starts with a summary of results for the model as a whole followed by a list of subsystems and charts that the model contains. Subsections on each subsystem and chart follow. Clicking the name of a subsystem or chart in the model summary takes you to a detailed report on that subsystem or chart. The section for each subsystem starts with a summary of the test coverage results for the subsystem and a list of the subsystems that it contains. The overview is followed by block reports, one for each block that contains a decision point in the subsystem.
Each section of the detailed report summarizes the results for the metrics used to test the object (model, subsystem, chart, block) to which the section applies. The sections for models and subsystems give results for the model and subsystem considered as a covered object and for the contents of the model or subsystem.
You can also access an individual object's subsection of the Details section from the Simulink® model as follows:
A pop-up menu appears.
In the pop-up menu, select Coverage, and from the resulting pop-up submenu, select Report.
The model coverage report appears, scrolled to the applicable Details subsection.
Each section can include coverage results for more than one simulation run. The report displays the results for each simulation run in a separate column. A numeric prefix in the column heading indicates the run that produced the data.
This table lists possible outcomes for a decision and the number of times that an outcome occurred in each test simulation.

The report highlights outcomes that did not occur in red. Clicking the block name causes the Simulink software to display the block diagram containing the block. It also highlights the block to help you find it in the diagram.
This table lists the number of occurrences of true and false conditions on each input port of a block.

This table lists the MC/DC input condition cases represented by the corresponding block and the extent to which the reported test cases cover the condition cases.

Each row of the table represents a condition case for a particular input to the block. A condition case for input n of a block is a combination of input values such that changing the value of input n alone is sufficient to change the value of the block's output. Input n is called the deciding input of the condition case.
The table uses a condition case expression to represent a condition case. A condition case expression is a character string where
The position of a character in the string corresponds to the input port number.
The character at the position represents the value of the input (T means true, F means false).
Boldfacing a character indicates that it corresponds to the value of the deciding input.
For example, FTF represents a condition case for a three-input block where the second input is the deciding input.
The table's Decision/Condition column specifies the deciding input for an input condition case. The #1 True Out column specifies the deciding input value that causes the block to output a true value for a condition case. The #1 True Out entry uses a condition case expression, for example, FF, to express the values of all the inputs to the block, with the value of the deciding variable indicated by boldfacing.
Parentheses around the expression indicate that the specified combination of inputs did not occur during the first (or only) test case included in this report. In other words, the test case did not cover the corresponding condition case. The #1 False Out column specifies the deciding input value that causes the block to output a false value and whether the value actually occurred during the first (or only) test case included in the report. The report adds additional #n True Out and #n False Out columns for additional test cases, where n is the number of the test case.
If you select Treat Simulink Logic blocks as short-circuited in the Coverage Settings dialog box (see Specifying Model Coverage Reporting Options), MC/DC coverage analysis does not check whether short-circuited inputs actually occur. The MC/DC details table uses an x in a condition expression (e.g., TFxxx) to indicate short-circuited inputs that were not analyzed by the tool.
Navigation Arrows. The section for each block contains a backward and a forward arrow. Clicking the forward arrow takes you to the next section in the report that lists an uncovered outcome. Clicking the back arrow takes you back to the previous uncovered outcome in the report.
![]() | Specifying Model Coverage Reporting Options | N-Dimensional Lookup Table Report | ![]() |
| © 1984-2008- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |