Probar la equivalencia de modelos
Las pruebas consecutivas, o pruebas de equivalencia, comparan los resultados de simulaciones normales en dos versiones o con los resultados del código generado de las simulaciones de software-in-the-loop (SIL), processor-in-the-loop (PIL) o hardware-in-the-loop (HIL). Puede generar pruebas consecutivas en Simulink Test™ que utilizan MCDC mejorada.
Temas
Pruebas de equivalencia consecutivas (B2B) para código generado
- 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.
Ejemplos destacados
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.
Debounce Temporal Properties
Model temporal system requirements for property proving and test case generation using Simulink® Design Verifier™ Temporal Operator blocks.
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.
