Create a test-specific simulation environment for your model by using a test harness. You can isolate individual blocks for unit testing and add inputs, verification logic, and dashboard blocks. Perform closed-loop testing by adding physical plant models to the test harness. Test potential design changes in the test harness before you change the production model.
Compared to using separate models for unit testing, test harnesses offer management and synchronization capabilities in the model canvas. If your model is under change management, you can save test harnesses in external files, without changing the main model.
You can test generated code by simulating test harnesses in SIL or PIL mode. You can also test external handwritten code by creating test harnesses for C Caller or S-Function blocks.
|Test Manager||Model and code testing in different execution environments, manage test suites, and analyze and report results|
Create and customize test harness configurations for your model and subsystem.
Manage test harnesses, including opening, converting, closing, deleting, and exporting.
Use Stateflow Chart to define test harness inputs and test sequence.
Test a Simulink® model in an isolated environment, using a separate workspace and configuration set accessed via the model canvas.
Transfer configuration sets and workspace variables, update the component design, and rebuild the harness to reflect the latest design.
Describes how test harnesses are constructed for certain Simulink semantics and component types.
Create reusable functions that customize test harnesses for your particular application, such as adding mixed source and sink block types and adding plant subsystems.
Import standalone models as test harnesses in Simulink Test™.
Test reusable components using tests for libraries, library blocks, and linked blocks.
Detect code errors, generate code metrics, test code and model equivalence, test code against requirements.
Debug and refine a subsystem using a simple test harness.