Requirements Condition Coverage Breakdown

Since R2022b

RequirementsConditionCoverageBreakdown

This metric returns the fraction of overall achieved condition coverage that comes from requirements-based tests.

You can collect this metric for the Units in your project. To control what the dashboard classifies as a unit, see Categorize Models in Hierarchy as Components or Units.

The metric:

Analyzes the overall aggregated coverage results.
Does not analyze coverage from tests that run in software-in-the-loop (SIL) or processor-in-the-loop (PIL) mode.

To collect data for this metric:

In the Model Testing Dashboard, in the Achieved Coverage Ratio section, point to the widget for Requirements-Based Tests, point to the three dots, and click the run button.
Use getMetrics with the metric ID RequirementsConditionCoverageBreakdown.

Collecting data for this metric loads the model file and test results files and requires a Simulink^® Coverage™ license.

For this metric, instances of metric.Result return the Value as a structure that contains these fields:

Numerator — The number of requirements-based tests that contribute to the overall achieved condition coverage.
Denominator — The total number of tests (requirements-based and non-requirements-based) that contribute to the overall achieved condition coverage.

The default compliance thresholds for this metric are:

Compliant — 100% of the overall achieved condition coverage comes from requirements-based tests
Non-Compliant — Less than 100% of the overall achieved condition coverage comes from requirements-based tests
Warning — None

See Also