Units in the Model Testing Dashboard
A unit is a functional entity in your software architecture that you can execute and test independently or as part of larger system tests. Software development standards, such as ISO 26262-6, define objectives for unit testing. Unit tests typically must cover each of the requirements for the unit and must demonstrate traceability between the requirements, the test cases, and the unit. Unit tests must also meet certain coverage objectives for the unit, such as modified condition/decision coverage.
You can label models as units in the Model Testing Dashboard. The dashboard then provides metric results for each unit. If you do not specify the models that are considered units, then the dashboard considers a model to be a unit if it does not reference other models.
In the Model Testing Dashboard, in the Artifacts panel, the unit dashboard icon indicates a unit. If a unit is referenced by a component, it appears under the component. If a unit references one or more other models, those models are part of the unit. The referenced models appear in the Design folder under the unit and contribute to the metric results for the unit.
To specify which models are units, label them in your project and configure the dashboard to recognize the label, as shown in Specify Models as Components and Units.
Components in the Model Testing Dashboard
A component is an entity that integrates multiple testable units together. For example:
A model that references multiple unit models could be a component model.
A System Composer™ architecture model could be a component. Supported architectures include System Composer architecture models, System Composer software architecture models, and AUTOSAR architectures.
A component could also integrate other components.
The Model Testing Dashboard organizes components and units under the components that reference them in the Artifacts panel. The dashboard does not provide metric results for components because components typically must meet different testing objectives than units.
If you do not specify the models that are considered components, then the dashboard considers a model to be a component if it references one or more other models.
In the Model Testing Dashboard, in the Artifacts panel, the component icon indicates a component. To see the units under a component, expand the component node by clicking the arrow next to the component icon.
To specify the models that are considered components, label them in your project and configure the dashboard to recognize the label, as shown in Specify Models as Components and Units.
Specify Models as Components and Units
You can control which models appear as units and components by labeling them in your project and configuring the Model Testing Dashboard to recognize the labels.
Open your project. For example, at the command line, type
dashboardCCProjectStart. This example project already has component and unit models configured.
In MATLAB®, at the bottom left of the Project window, right-click in the Labels pane and click Create New Category. Type a name for the category that will contain your testing architecture labels, for example,
Testing Interfaceand then click Create.
Create a label for the units. On the Labels pane, right-click the category that you created and click Create New Label. Type the label name
Software Unitand click OK.
Create another label for component models and name the label
The unit and component labels appear under the category in the Labels pane.
Label the models in the project as components and units. In the project pane, right-click a model and click Add label. In the dialog box, select the label and click OK. For this example, apply these labels:
db_Controller— Software Component
db_ControlMode— Software Unit
db_DriverSwRequest— Software Unit
db_LightControl— Software Unit
db_TargetSpeedThrottle— Software Unit
To open the Model Testing Dashboard, use one of these approaches:
On the Project tab, in the Tools section, click Model Testing Dashboard.
At the MATLAB command line, enter
In the Dashboard tab, click Options.
In the Project Options dialog box, in the Classification section, specify the category and labels that you created for the components and units. For the component interface, set Category to
Testing Interfaceand Label to
Software Component. For the unit interface, set Category to
Testing Interfaceand Label to
Click Apply. The dashboard updates the traceability information in the Artifacts panel and organizes the models under the component models that reference them. If a model is not referenced by a component, it appears at the top level with the components.
For each unit, the dashboard shows the artifacts that trace to the unit. To view the metric results for a unit, click the unit name in the Artifacts panel. The dashboard shows the model testing metric results for the unit that you select.
Trace Artifacts to Units for Model Testing Analysis
To determine which artifacts are in the scope of a unit, the Model Testing Dashboard analyzes the traceability links between the artifacts and the software unit models in the project. The Artifacts panel lists the units, organized by the components that reference them. Under each unit, the panel shows these artifacts that trace to the unit:
To see the traceability path that the dashboard found from an artifact to its unit,
right-click the artifact and click View trace to unit. A traceability
graph opens in a new tab in the Model Testing Dashboard. The graph shows the connections and
intermediate artifacts that the dashboard traced from the unit to the artifact. To see the
type of traceability that connects two artifacts, place your cursor over the arrow that
connects the artifacts. The traceability relationship is either one artifact containing the
other or one artifact tracing to the other. For example, for the unit
db_DriverSwRequest, expand Functional Requirements > Upstream > db_SystemReqs.slreqx. Right-click the requirement for Target speed increment
and click View trace to unit. The trace view shows that the unit
db_DriverSwRequest traces to the implemented functional requirement
Switch precedence, which traces to the upstream functional
Target speed increment.
Under the list of components is the folder Trace Issues which contains unexpected requirement links, requirements links which are broken or not supported by the dashboard, and artifacts that the dashboard cannot trace to a unit. To help identify the type of tracing issue, the folder Trace Issues contains subfolders for Unexpected Implementation Links, Unresolved and Unsupported Links, Untraced Tests, and Untraced Results. For more information, see Fix Requirements-Based Testing Issues.
If an artifact returns an error during traceability analysis, the panel includes the artifact in an Errors folder. Use the traceability information in these sections and in the units to check if the testing artifacts trace to the units that you expect. To see details about the warnings and errors that the dashboard finds during artifact analysis, at the bottom of the Model Testing Dashboard dialog, click Diagnostics.
As you edit and save the artifacts in your project, the dashboard tracks your changes and indicates if the traceability data in the Artifacts panel might be stale by showing a warning banner. To update the traceability data, click the Trace Artifacts button on the warning banner.
The folder Functional Requirements shows requirements of
Functional that are either implemented by or upstream of the
When you collect metric results for a unit, the dashboard analyzes only functional requirements that the unit directly implements. The folder Functional Requirements contains two subfolders to help identify which requirements are implemented by the unit or are upstream of the unit:
Implemented — Functional requirements that are directly linked to the unit with a link Type of
Implements. The dashboard uses these requirements in the metrics for the unit.
Upstream — Functional requirements that are indirectly or transitively linked to the implemented requirements. The dashboard does not use these requirements in the metrics for the unit.
If a requirement does not trace to a unit, it appears in the Trace Issues folder. If a requirement does not appear in the Artifacts panel when you expect it to, see Requirement Missing from Artifacts Panel.
Use the Requirements Toolbox™ to create or import the requirements in a requirements file
The folder Design shows:
The model file that contains the block diagram for the unit.
Models that the unit references.
Libraries that are partially or fully used by the model.
Data dictionaries that are linked to the model.
The folder Tests shows test cases and test harness that trace to the unit. This includes test cases that run on the unit and test cases that run on subsystems in the unit model by using test harnesses.
When you collect metric results for a unit, the dashboard analyzes only test cases that run on the unit model or unit model subsystems. The folder Tests contains subfolders to help identify which test cases are testing the unit and which test harnesses trace to the unit:
Unit Tests — Test cases that the dashboard considers as unit tests. A unit test directly tests either the entire unit model or the model subsystems. The dashboard uses these tests in the metrics for the unit.
Others — Test cases that trace to the unit but that the dashboard does not consider as unit tests. For example, the dashboard does not consider tests on a library to be unit tests. The dashboard does not use these tests in the metrics for the unit.
Test Harnesses — External test harnesses that trace to the unit or unit subsystems. Double-click a test harness to open it.
If a test case does not trace to a unit, it appears in the Trace Issues folder. If a test case does not appear in the Artifacts panel when you expect it to, see Test Case Missing from Artifacts Panel. For troubleshooting test cases in metric results, see Fix a test case that does not produce metric results.
Create test cases in a test suite file by using Simulink® Test™.
When you collect metric results for a unit, the dashboard analyzes only the test results from unit tests. The folder Test Results contains two subfolders to help identify which test results are from unit tests:
Unit Simulation — Simulation results from unit tests. The dashboard uses these results in the metrics for the unit.
The following types of test results are shown:
Saved test results — results that you have collected in the Test Manager and have exported to a results file.
Temporary test results — results that you have collected in the Test Manager but have not exported to a results file. When you export the results from the Test Manager the dashboard analyzes the saved results instead of the temporary results. Additionally, the dashboard stops recognizing the temporary results when you close the project or close the result set in the Simulink Test Result Explorer. If you want to analyze the results in a subsequent test session or project session, export the results to a results file.
Others — Results that are not simulation results, are not from unit tests, or are only reports. For example, SIL results are not simulation results. The dashboard does not use these results in the metrics for the unit.
If a test result does not trace to a unit, it appears in the Trace Issues folder. If a test result does not appear in the Artifacts panel when you expect it to, see Test Result Missing from Artifacts Panel. For troubleshooting test results in dashboard metric results, see Fix a test result that does not produce metric results.
The folder Trace Issues shows artifacts that the dashboard has not traced to units. Use the folder Trace Issues to check if artifacts are missing traceability to the units. The folder Trace Issues contains subfolders to help identify the type of tracing issue:
Unexpected Implementation Links — Requirement links of Type
Implementsfor a requirement of Type
Informational. The dashboard does not expect these links to be of Type
Implementsbecause container requirements and informational requirements do not contribute to the Implementation and Verification status of the requirement set that they are in. If a requirement is not meant to be implemented, you can change the link type. For example, you can change a requirement of Type
Informationalto have a link of Type
Unresolved and Unsupported Links — Requirements links that are either broken in the project or not supported by the dashboard. For example:
If a model block implements a requirement, but you delete the model block, the requirement link is now unresolved.
If a requirement links to or from a data dictionary, the link is not supported and the Model Testing Dashboard does not trace the link.
The Model Testing Dashboard does not support traceability analysis for some artifacts and some links. If you expect a link to trace to a unit and it does not, see the troubleshooting solutions in Resolve Missing Artifacts, Links, and Results in the Model Testing Dashboard.
Untraced Tests — Tests that execute on models or subsystems that are not on the project path.
Untraced Results — Results that the dashboard cannot trace to a test case. For example, if a test case produces a result, but you delete the test case, the dashboard cannot trace the results to the test case.
When you add traceability to an artifact, the dashboard detects this and shows a warning banner at the top of the dashboard to indicate that the artifact traceability shown in the Artifacts panel is outdated. Click the Trace Artifacts button on the warning banner to refresh the data in the Artifacts panel.
The Model Testing Dashboard does not support traceability analysis for some artifacts and some links. If an artifact is untraced when you expect it to trace to a unit, see the troubleshooting solutions in Trace Issues.
The folder Errors appears if artifacts returned errors when the dashboard performed artifact analysis. These are some errors that artifacts might return during traceability analysis:
An artifact returns an error if it has unsaved changes when traceability analysis starts.
A test results file returns an error if it was saved in a previous version of Simulink.
A model returns an error if it is not on the search path.
Open these artifacts and fix the errors. The dashboard detects changes to the artifacts and shows a warning banner at the top of the dashboard to indicate that the artifact traceability shown in the Artifacts panel is outdated. Click the Trace Artifacts button on the warning banner to refresh the data in the Artifacts panel.
To see details about artifacts that cause errors, warnings, and informational messages during analysis, at the bottom of the Model Testing Dashboard dialog, click Diagnostics. You can filter the diagnostic messages by their type: Error, Warning, and Info. You can also clear the messages from the viewer.
The diagnostic messages show:
Modeling constructs that the dashboard does not support
Links that the dashboard does not trace
Test harnesses or cases that the dashboard does not support
Test results missing coverage or simulation results
Artifacts that return errors when the dashboard loads them
Information about model callbacks that the dashboard deactivates
Files that have file shadowing or path traceability issues
Artifacts that are not on the path and are not considered during tracing