White Papers > Testing TargetLink Models and C Code with Reactis

Download: PDF  


1  Introduction

Reactis provides model-based testing and validation of discrete-time embedded-controller models in the Simulink / Stateflow notation developed by MathWorks. The dSPACE autocode tool TargetLink has become popular because:

  • its Simulink-compatible blockset enables detailed specification of the C code attributes, and
  • the C code generated from TargetLink models is very high quality.

With proper configuration, Reactis can work with not only the TargetLink blockset (of many versions of TargetLink), but also with the C code it generates. This has many obvious advantages:

  • Direct comparison between idealized-model behavior and realized C-code behavior.
  • Reactis test vectors derived for model-coverage can be used to analyze code coverage in the same environment. This can be extremely useful when looking at boundary or threshold conditions.
  • Interactive analysis using the full step-accurate debugging capability of Reactis.

A model-based design environment involving Reactis and TargetLink is depicted in Figure 1. Reactis contains three core components: Tester, which offers automatic test generation from models; Simulator, which enables users to visualize model execution to debug models and track coverage; and Validator, which offers automated checks of models for violations of user-specified requirements. For more information on the basic capabilities of Reactis, please see [RSI10].

Diagram showing the stages
of a V model-based design process: design activities coming down the left and testing 
activities going up the right.
Figure 1: Reactis in a model-based design process.