Test harneses provide a separate simulation environment for testing a model or component. Configure test harnesses with sources, sinks, and sychronization properties to match your verification activities. For models used for production code generation, you can isolate your test inputs, verification logic, and signal logging to preserve code generation semantics. For models under change management, you can preserve the model version by using externally saved test harnesses.
|Compare component under test between harness model and main model|
|Copy test harness|
|Close test harness|
|Convert test harnesses between internal and external storage|
|Create test harness|
|Delete test harness|
|Export test harness to Simulink model|
|Import Simulink model to test harness|
|Find test harnesses in model|
|Load test harness|
|Move test harness from linked instance to library block or to a different harness owner|
|Open test harness|
|Push test harness workspace entries and configuration set to model|
|Rebuild test harness and update workspace entries and configuration parameter set based on main model|
|Change test harness property|
Create and customize test harness configurations for your model and subsystem.
Describes how test harnesses are constructed for certain Simulink® semantics and component types.
Import standalone models as test harnesses in Simulink Test™.
Manage test harnesses, including opening, converting, closing, deleting, and exporting.
Create reusable functions that customize test harnesses for your particular application, such as adding mixed source and sink block types and adding plant subsystems.
Test a Simulink model in an isolated environment, using a separate workspace and configuration set accessed via the model canvas.
Resolve parameters and signals between test harness and model.
Transfer configuration sets and workspace variables, update the component design, and rebuild the harness to reflect the latest design.
Review support for particular model elements and semantics, and automatic syntax suggestions in the Test Sequence Editor.