Simulink Coverage

Screenshot of coverage details for a Simulink block within the Simulink canvas.

Model Coverage

Measure how much of your design is covered by simulation testing to assess testing effectiveness and completeness. Analyze coverage collected during requirements-based testing to determine if there are any gaps in testing, missing requirements, or unintended functionality.

Coverage of custom code used in a Simulink model.

Code Coverage

Measure coverage for software-in-the-loop (SIL) and processor-in-the-loop (PIL) tests of code generated with Embedded Coder or for code called within Simulink models.

Screenshot of aggregated coverage results and checkbox to scope the results to requirements.

Manage Aggregated Coverage Results

Aggregate coverage from multiple simulations. View system test coverage achieved from unit tests. Scope results to linked requirements to avoid unintended coverage.

Screenshot of several structural and non-structural coverage metric choices.

Coverage Metrics

Measure model and code coverage for a variety of metrics, including decision, condition, MCDC, relational boundary, and signal range.

Screenshot of filtering out missing coverage to focus on what you want to test.

Reconcile Missing Coverage

Filter model constructs that prevent full test coverage, such as defensive modeling patterns, to focus on testing other parts of your design.

Coverage details, including traceability to tests, from a detailed report.

Generate Coverage Reports

Generate detailed reports that include accumulated coverage results on selected metrics. View requirements traceability details for model elements and tests.

Simulink Coverage FAQs

Simulink Coverage performs model and code coverage analysis that measures testing completeness in models and generated code using industry-standard metrics.

It supports decision, condition, modified condition/decision coverage (MCDC), relational boundary coverage, signal range coverage, and lookup table coverage metrics.

You can use missing coverage data to identify gaps in testing, missing requirements, or unintended functionality in your models and generated code.

Yes, it measures coverage for software-in-the-loop (SIL) and processor-in-the-loop (PIL) tests of code generated with Embedded Coder, as well as C/C++ S-functions and MATLAB functions called within Simulink models.

Yes, you can accumulate coverage data from multiple simulations and view coverage achieved through both unit and system tests.

It produces interactive reports and highlights coverage results directly in blocks and subsystems to visualize gaps in testing.

Yes, you can apply filters to exclude blocks from coverage and justify missing coverage in reports, such as defensive modeling patterns.