Reactis Testing Tools for Simulink and C Code

Model-Based Design with Simulink^® and Stateflow^®

C Code Process

Coverage metrics include generic objectives such as Decision, Condition, and Modified Condition/Decision Coverage (MC/DC), Simulink-specific measures such as branch and subsystem, and Stateflow-specific metrics such as state, condition-action, and transition-action.

Testing code (auto-generated or hand-written) against your model is easy with Reactis:

1. Generate tests from model
2. Run tests on code
3. Differences are automatically detected and flagged.

Coverage metrics include Statement, Decision, Condition, and Modified Condition/Decision Coverage (MC/DC).

As Reactis Tester generates tests, it performs an array of checks to flag runtime errors in your C code. Memory errors are particularly easy to make in C and can be very hard to debug. A memory error occurs whenever a program reads-from or writes-to an invalid address. Memory errors are particularly common in C programs because the C programming language gives the programmer direct access to the program's memory, which can boost performance but also allows software defects to access arbitrary memory locations.

Some errors flagged by Reactis include out-of-bounds array indexes, buffer overruns, dangling heap pointers (accessing a region of heap-allocated memory after the memory has been freed), dangling stack pointers (accessing a pointer to a local variable of a function after the function has returned) and the use of pointers cast from incorrect numeric values. Reactis Tester not only detects these types of errors, it returns a test that can be executed in Reactis Simulator to pinpoint the underlying cause of the error.

• Execute a block, single step, or multiple steps at a time.
• Reverse execution.
• To see data values, hover with the mouse, open a scope, or add to watched variables.
• Unexercised parts of model are highlighted in red.
• Generate detailed coverage reports.
• Breakpoints.
• When using the Reactis for C Plugin or the Reactis for EML Plugin, its like having an advanced source code debugger right in your Simulink environment. Debugging Simulink, Stateflow, Embedded MATLAB, and C code is all controlled from the same simple interface.

• Execute a single statement; step into, over, out of functions; execute a full step or multiple steps at a time.
• Reverse execution.
• To see data values, hover with the mouse, open a scope, or add to watched variables.
• Unexercised parts of code are highlighted in red.
• Generate detailed coverage reports.
• Breakpoints.

Validator gives a user two ways to define a check: as simple textual expressions similar to the assert capabilities found in programming languages, or as a Simulink / Stateflow model. In the latter case, the model implementing the checks is intended to monitor the behavior of the controller model and raise flags if any violations are discovered.

Eliminating runtime errors is important, but only one step towards high-quality software. A program that does not crash, but does the wrong thing is also unacceptable. Reactis Validator gives you a way to formulate and perform checks that your program is operating properly. Checks are formulated in a way similar to the assert mechanism of C.

• System Requirements
• Simulink and Stateflow support

• System Requirements

• Testing and Validation of Simulink Models with Reactis
• Testing TargetLink Models and C Code with Reactis
• Achieving ISO 26262 Compliance with Reactis

• Finding Bugs in C Code with Reactis for C

• Reactis User's Guide

• Reactis for C User's Guide

• Reactis Communicator
• Reactis Patches