Skip to main content
Ctrl+K
Reactive Systems logo

Finding Bugs in C Code with Reactis for C

  • 1. Introduction
  • 2. Reactis Tester
  • 3. Reactis Simulator
  • 4. Reactis Validator
  • 5. Finding and Fixing Runtime Errors
  • 6. Regression Testing
  • 7. Synergy with Reactis for Simulink
  • 8. Conclusions
  • .md

Synergy with Reactis for Simulink

7. Synergy with Reactis for Simulink#

Combining Reactis for C with Reactis for Simulink in a model-based development process produces synergistic benefits.

Engineers performing model-based design using Simulink®/Stateflow®[1] as a design tool and C as an implementation language can benefit significantly from using Reactis for C in combination with its sibling product, Reactis for Simulink.

_images/back-to-back-testing.png

Fig. 7.1 Checking for conformance of a C program to a Simulink model, often called back-to-back testing.#

Synergistic benefits occur when test suites are shared between both versions of Reactis. There are two basic use-case scenarios. The first case is shown in Figure 7.1, which depicts the workflow in a typical model-based development environment. In this scenario, the conformance of an implementation to a model can be checked by generating a test suite using Reactis for Simulink, and then testing the implementation against the test suite with Reactis for C.

_images/reverse-engineering.png

Fig. 7.2 Checking for conformance of a model to the C code from which the model was reverse engineered.#

Figure 7.2 shows the workflow when using both Reactis products to support the reverse engineering of models from legacy C code. In this scenario, the conformance of the model to the legacy implementation can be checked by generating a test suite from the implementation using Reactis for C, and then testing the model against the test suite using Reactis for Simulink.


[1]

Simulink and Stateflow are registered trademarks of MathWorks, Inc.

previous

6. Regression Testing

next

8. Conclusions

By Reactive Systems, Inc.

© Copyright 2006-2023.