Glossary of Reactis Concepts

6. Glossary of Reactis Concepts#

In addition to browsing the model itself, Reactis Model Inspector lets you examine various testing and validation artifacts created in Reactis. Reactis is a separate product of Reactive Systems that supports automated testing and validation of Simulink models. This chapter provides a brief description of Reactis artifacts that can be examined in Reactis Model Inspector. For more complete descriptions, please see the Reactis User’s Guide, available at:

https://reactive-systems.com/doc/reactis-for-simulink/

Throughout this chapter, the notation RUG:9 denotes Chapter 9 and the notation RUG:7.2 denotes Section 7.2 of the Reactis User’s Guide.

Configuration Variable.: A configuration variable is a workspace variable tagged in Reactis to be changed in between tests, but not during a test. See RUG:5.4.

Inport Type.: Reactis lets you assign a type or constraint to a top-level inport that will limit the values that will be used for the inport for testing and validation. For example, you can limit values for an inport to a range by specifying a minimum and maximum value. Type constraints are manipulated from the Inport Types tab of the Reactis Info File Editor and may be viewed from that tab in Reactis Model Inspector. See RUG:5.3.

Reactis Makefile.: A Reactis Makefile (.rsm file) lists the C files that comprise a library that implements an S-Function or is used by an S-Function or Stateflow custom code. See RUG:16.
Reactis Simulator.: Simulator is a component of Reactis that supports interactive simulation and debug of models. See RUG:7.
Reactis Tester: Component of Reactis that generates comprehensive yet compact test suites from models. See RUG:8.
Reactis Validator: Component of Reactis that checks if a model satisfies its requirements. See RUG:9.

Test Point: A Test point is an internal data item, such as a Simulink block, Simulink signal, or Stateflow variable, that Reactis treats as a virtual output. Reactis Tester records the values of test points in test suites and Reactis Simulator flags any differences between the values computed by a model for a test point and those stored in a test suite. See RUG:5.5.

Test Suite: Test suites are the most important artifact created with Reactis. A test suite is comprised of a set of tests. Each test in the suite corresponds to a simulation run of the model that captures the top-level inputs and outputs at each simulation step. Comprehensive yet compact test suites are generated automatically by Reactis Tester. Reactis Simulator lets you execute tests in order to debug your model. When Reactis Validator finds a violation of a requirement it returns a test that you can execute in Simulator in order to diagnose the problem. Reactis Model Inspector lets you inspect tests using the Test Suite Browser.

Validator Objective: Using Reactis Validator you can instrument your model with Validator Objectives in order to check that your model satisfies its requirements. Validator Objectives include assertions, user-define targets, and virtual sources. See RUG:9.

Virtual Source: A virtual source is a Validator objective that lets you control a top-level inport of your model. See RUG:9.