Model Objects That Do Not Receive Coverage
R2026bSimulink® Coverage™ does not analyze decision, condition, MCDC, or relational boundary coverage for blocks that are not listed in Model Objects That Receive Coverage.
Note
Simulink
Coverage does not record model coverage when the Simulation
mode parameter is set to Rapid
Accelerator. If you have an Embedded Coder® license, Simulink
Coverage can measure the coverage of code generated from models in
software-in-the-loop (SIL) or processor-in-the-loop (PIL) mode. For more
information, see Code Coverage for Models in Software-in-the-Loop (SIL) Mode and Processor-in-the-Loop (PIL) Mode.
This table identifies specific model objects that do not receive coverage.
| Model object | Reason or Limitation |
|---|---|
Logical Operator block | Logical Operator blocks do not receive coverage when the
Operator parameter specifies
|
Model block | Model blocks do not receive coverage when:
|
| Protected model block | Simulink Coverage does not analyze protected model blocks. For more information about protected model blocks, Model Protection (Simulink Coder). |
Subsystem block | Subsystem blocks do not receive coverage when the Read/Write
Permissions parameter is set to
|
Stateflow® chart MATLAB® Function block | Stateflow elements and MATLAB Function blocks do not receive coverage when debugging/animation is not enabled for the model or object. |
Virtual blocks | Virtual blocks do not receive coverage. For more information, see Nonvirtual and Virtual Blocks. |
| MATLAB Files | MATLAB files that are obfuscated, such as by using the
|
Blocks that do not contribute to run-time behavior | Blocks that do not contribute to run-time behavior do not receive coverage. For example, Check Signal Attributes block, blocks that handle data type propagation such as Data Type Propagation block, etc. |