How to Analyze Coverage Using Test Case Traceability

Model coverage and code coverage measure how much of your Simulink models and generated code were exercised during simulation.

In this video, I’ll show you how to use Simulink Test and Simulink Coverage to analyze missing coverage using test case traceability data in the coverage report.

Here is a test suite I am managing using Simulink Test. This test suite contains requirements-based tests for a Cruise Control algorithm implemented using Stateflow. Each test case is linked to requirements managed in Requirements Toolbox.

After running the test suite, I can first view the overall coverage results in the Test Manager. For more details, I can generate a Coverage Report to see which parts of the design were exercised during simulation. I can also see which tests achieved a given coverage objective.

Let’s look at the coverage for the “ON” state.

This section of the coverage report shows the coverage objectives associated with the “ON” state, as well as which test case initially achieved each coverage objective. 

There is an uncovered objective for the “Accel” substate. We can see in the table that the “Accel” substate was partially exercised by test case T3. A simple next step is to look at test case T3 by clicking on the hyperlink in the table to see how we could supplement that test case to completely cover the “Accel” substate

Once I have finished testing my model, I can run tests on the generated code by simulating the model in Software-in-the-Loop mode. I can use the same approach I used while testing the model by looking at the test case traceability data in the coverage report.

This example showed how to use test case traceability data in the coverage report to understand how to fully exercise your Simulink models and generated code.

Click on the link below to try the example.

For more information, please visit the Simulink Coverage product page on mathworks.com