Automated Testing and Validation with Reactis®

 Reactis User's Guide   Contents  |  Index
 Chapters:  1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | A | B | C

Appendix C  Revision History

Different versions of Reactis are labeled as shown in Figure C.1 and described below.

Figure C.1: Version labels begin with a “V” and include three parts: a year, a major release number, and a patch release number. The parts are numbers separated by decimal points. By convention, trailing zeros are omitted.

Major Releases.
A new version of Reactis is released at the start of each year and labeled by a “V” followed by the four-digit year, for example V2016. Each label for an intra-year release includes a suffix consisting of a decimal point followed by a major release number; for example V2016.1, V2016.2, etc. will label the releases during 2016 that follow V2016.
Beta Releases.
RSI often makes beta releases available to customers interested in evaluating the newest features of Reactis. Beta releases do not undergo as much testing as major releases do. By convention, beta releases have odd numbered major release numbers. For example, V2016.1, and V2016.3 denote beta releases.
Patch Releases.
Both stable and beta releases may be patched. The label for a patch release is constructed by extending the label for the major release to be patched with a suffix that includes a second decimal point and a patch release number. For example:
V2017.0.1denotesthe first patch release for V2017
V2016.2.3denotesthe third patch release for V2016.2

C.1  Patches Mailing List Archive

Patches to Reactis are posted to the Reactive Systems website every two to four weeks on average. To view a summary recent changes, please view the archives of the Reactis Patches mailing list available at:

C.2  V2017.2 (22 December 2017)

The V2017.2 release of Reactis includes the bug fixes that were included in releases V2017.0.1 through V2017.0.3 plus the new features listed below.

C.2.1  Newly Supported Simulink Features

The following Simulink features are supported in Reactis V2017.2:

  • MATLAB R2017b.
  • Permute Dimensions block.

C.2.2  Tester Optimizations

Generated test suites achieve same level of coverage with fewer tests and overall steps. For some models, the number of tests in a suite is reduced by 90%.

C.2.3  Conditional Input Constraints

The static input constraints available so far in Reactis do not allow the user to specify constraints that depend on simulation time. For example, a reset input may only be supposed to become “true” for a short time at the beginning of the simulation. So far it was not possible to model this behavior within the input type constraints.

Reactis V2017.2 introduces a new concept of conditional input constraints, where constraints can depend on the current simulation time. In the example of the reset input mentioned above, a type constraint of

if t<0.1 then boolean{true} else boolean{false}

will force that input port to be true for the first 0.1 seconds and then switch to false.

C.2.4  Scope Signal Groups

Reactis V2017.2 allows multiple signals to be shown within the same window where each signal has its own display and scaling but a shared time axis. This improves on the previous displays where all signals within the same scope window shared the same scaling, causing small signals to become overpowered by larget signals.

C.2.5  API improvements

  • rsSimImportSuite recognizes flag “-M” to only import a suite if inputs and outputs match the current model. If the flag is not given, Reactis will adjust the imported data by leaving out input data from the test suite not used in the model and adding random values for data required by the model but not available in the test data.
  • Added rsGUI API function to start Reactis GUI from the MATLAB command line.
  • Added rsRsiRange, rsRsiSet, rsRsiDelta functions to simplify setting type constraints via the API.
  • Added rsRsiIfThenElse function to support setting conditional input constraints.

C.2.6  Reactis for EML Plugin

  • Support dynamic creation of structure values

C.2.7  Test Execution Report Enhancements

The Test Execution Report now has an option to include a step-by-step listing of the coverage targets that were covered in each step.

C.2.8  Other Enhancements

  • Referenced models now inherit import settings from their parent model. This significantly reduces the setup necessary for models using model referencing.
  • Added option to not show empty subsystems in the hierarchy panel.
  • Variables in the watched variable panel are highlighted when their value changes.
  • Coverage tracking can now be disabled for all targets within Validator Diagram Objectives.
  • Reactis can now import fixpoint information such as slope and bias as well as ranges from the TargetLink data dictionary.
  • When importing test points, Reactis can import signal ranges set in Simulink.signal objects and automatically create assertions to monitor the ranges during test case generation.
  • Added option to use signal name (instead of block name) for imported test points.
  • Test points now break up conditional input branches and multi-block MC/DC groups, allowing coverage tracked for a model to better match coverage of corresponding C code.
  • A new option allows to exclude the “equal” case when tracking relational operator boundary coverage.
  • When exporting to CSV, strip out the “(1)(1)” suffix for 1x1 matrices.
  • Draw relational operator and constant on Compare To Constant blocks.

C.3  Previous Major Release Dates

Major releases of Reactis prior to V2017.2 have occurred on the following dates:

VersionRelease Date