Documentation

Coverage data is collected during simulation.

Coverage data is not collected during simulation.

Coverage data is collected for the top-level model, as well as all supported subsystems and model references.

Coverage data is collected for one or more referenced models. To specify the referenced models, use the parameter Select Models. You can also specify the top-level model itself.

Coverage data is collected for a specific subsystem. To specify a subsystem, use the parameter Select Subsystem.

Coverage data is collected for MATLAB functions in external MATLAB files. The functions can be called from MATLAB Function blocks or Stateflow charts in the model.

Coverage data is not collected for external MATLAB files.

Coverage data is collected for C/C++ code in S-Function blocks in the model.

Coverage data is not collected for C/C++ code used in the model.

The analysis computes decision coverage during simulation

Decision coverage analysis checks blocks that perform an action based on whether an operation evaluates to true or false. For instance, the Abs block first evaluates if the input is less than zero and acts accordingly. For each operation that can evaluate to true or false, the analysis reports what fraction of the outcomes was true during simulation and what fraction was false.

See Decision Coverage (DC).

The analysis computes condition and decision coverage during simulation.

Condition coverage analysis checks blocks that output a logical combination of their inputs (such as Logical Operator blocks). For each block, the analysis records what fraction of the inputs was true during simulation and what fraction was false.

See Condition Coverage (CC).

The analysis computes Modified Condition/Decision Coverage (MCDC) during simulation.

See Modified Condition/Decision Coverage (MCDC).

The analysis checks if each block executes at least once during simulation.

See Execution Coverage (EC).

Blocks with lookup tables are checked for coverage. A test case achieves full coverage of a lookup table if it executes each interval of the table at least once.

Lookup table coverage is not recorded.

Maximum and minimum signal values are recorded for each block that has an output signal.

Signal range information is not recorded.

Maximum, minimum and allocated signal size are recorded for each block that has a variable-size output signal. See Variable-Size Signal Basics (Simulink).

Signal size information is not recorded.

Through Simulink Design Verifier blocks, you can specify objectives and constraints in your model. To check if these objectives are satisfied, you first generate test cases using these blocks. You can execute these test cases on the original model and record whether the specified objective was satisfied at least once. To record this coverage, enable this parameter.

For an example, see Simulink Design Verifier Coverage.

Coverage information is not recorded for Simulink Design Verifier blocks.

For certain blocks, such as the Abs block, you can specify that they must saturate on integer overflow. If you enable this parameter, the number of times these blocks saturate during simulation is recorded.

Saturation on integer overflow information is not recorded.

Certain blocks such as the Relational Operator or If block use a relational operation. If you enable this parameter, the coverage analysis checks if these operations are executed with equal (integer) or almost equal (floating-point) values.

Relational boundary coverage information is not recorded.

Coverage is recorded only for the time interval that you specify. To specify a time interval, use these parameters:

Coverage is recorded for the entire duration of simulation.

Coverage is recorded for every supported block in the model. The value of the configuration parameter Block reduction is ignored. See Block reduction (Simulink).

Coverage is not recorded for blocks that are effectively removed from the model because of block reduction. For instance, coverage is not recorded for a block that is reduced by dead code elimination.

Coverage analysis does not consider the input to a logical operation that is rendered redundant by another input.

Coverage analysis considers all inputs to a logical operation.

Use masking MCDC analysis. To establish the independence of inputs, masking MCDC analysis does not require that all other inputs be strictly held constant while one input is varied. Therefore, masking MCDC analysis allows you to satisfy greater number of objectives in a given simulation.

Use unique-cause MCDC analysis.

Provide a warning when blocks in the model are not supported for coverage analysis.

Do not provide a warning for unsupported blocks.

Simulink collects model coverage data during simulation.

Model coverage data is not collected or reported.

Coverage data is collected for the top-level model.

Coverage data is not collected for the top-level model.