Test Model Equivalence

Test behavioral equivalence of model and generated code, or models run in different Simulink^® releases

Back-to-back tests, or equivalence tests, compare the results of normal simulations across two releases or with the generated code results from software-in-the-loop (SIL), processor-in-the-loop (PIL), or hardware-in-the-loop (HIL) simulations. You can generate back-to-back tests in Simulink Test™ that use Enhanced MCDC.

Topics

Back-to-Back (B2B) Equivalence Testing for Generated Code

Analyze Code and Perform Software-in-the-Loop Testing
Detect code errors, generate code metrics, test code and model equivalence, test code against requirements.
Create Back-to-Back Tests Using Enhanced MCDC
Create and run equivalence tests using enhanced MCDC.

Verify Model Behaves Numerically Equivalent Release-on-Release

Create and Run Back-to-Back Tests Using Enhanced MCDC
Create back-to-back tests using enhanced MCDC in Test Manager.

Featured Examples

Generate Parameters Values

Tune parameters using parameter configuration file for Simulink® Design Verifier™ analysis. The model contains the parameter control_mode that enables the active controller and selects its output to be the model output. Simulink Design Verifier treats this parameter as an input that is constrained to be either 1 or 2 and generates the appropriate value for each test case.

Open Script

Debounce Temporal Properties

Model temporal system requirements for property proving and test case generation using Simulink® Design Verifier™ Temporal Operator blocks.

Open Script

Power Window Controller Temporal Properties

Model temporal system requirements in a power window controller model for property proving and test case generation using Simulink® Design Verifier™ Temporal Operator blocks.

Open Script