Generate comprehensive tests with Reactis

Reactis V2024

Highlights Download

How Do You Develop and Test Software?

Model-Based Design with Simulink® and Stateflow®

Reactis icon Reactis plays a number of important roles in a model-based design process. It gives you a set of tools to test, verify, and truly understand your model's behavior and can help you check whether the source code that will ultimately be deployed conforms to the behavior of your model. More on testing and validation of Simulink models.

Reactis for EML Plugin integrates seamlessly with Reactis to offer white-box testing of any portions of your model implemented with Embedded MATLAB®, e.g. MATLAB Function blocks and the MATLAB action language in Stateflow.

Reactis for C Plugin integrates seamlessly with Reactis to offer white-box analysis of the C code portions of models (C Caller blocks, S-Functions and Stateflow custom code). More on C Caller block, S-Function, and custom code debug.

Reactis and the C Plugin also support testing TargetLink® models and C code.

Reactis Model Inspector icon Reactis Model Inspector offers a low-cost, lightweight Simulink viewer.

C Code

Reactis for C icon Reactis for C generates comprehensive yet compact tests from C code, detects runtime errors, and tracks coverage (Statement, Decision, Condition, MC/DC, MCC). When an error is detected, you can easily replay a concrete execution sequence leading to the problem in order to understand, diagnose, and fix the bug. More on testing C code.

Diagram showing Reactis generating test suite given C code as input

Back-to-Back Testing of Code Against Simulink Model

  1. Generate tests from Simulink model
  2. Run tests on code
  3. Differences are automatically detected, flagged, and recorded in reports.
Diagram showing back to back testing of C code against model.  Simulink model flows into Reactis Tester which outputs a test suite.  That test suite is subsequently run on C code in Reactis for C.



Reactis Helps with Hard Questions

Will unexpected inputs cause a runtime error?

How much of my code have I really tested?

How do I understand, diagnose, and fix a bug?

Will the brake always deactivate the cruise control?

How do I test my code against the model?