24. Revision History#

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

_images/versionLabel.png

Fig. 24.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

There are two major Reactis releases each year, for example, V2025 and V2025.2.

Beta Releases

Reactive Systems sometimes 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, V2025.1, and V2025.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:

V2025.0.1

denotes the first patch release for V2025

V2025.2.3

denotes the third patch release for V2025.2

24.1. Patches Mailing List Archive#

Patches to Reactis are posted to the Reactive Systems website between major releases. To view a summary of recent changes, please view the archives of the Reactis Patches mailing list available at:

https://reactive-systems.com/patches/archive

24.2. V2026 (10 June 2026)#

V2026 includes the bug fixes that were included in patch releases through V2025.2.2, plus the new features listed below.

24.2.1. Improved Static Analysis and Test Generation#

A number of improvements have been made to static model reachability analysis and solver capabilities during test case generation. The goal of these enhancements is to identify more targets as unreachable (and more assertions as impossible to violate) during static analysis and to enable Tester to cover more targets during test generation. The changes include the following:

  • New model-specific settings to configure how much time Reactis should spend on reachability analysis when starting Simulator and Tester. This allows more time to be allocated for a model with a high number of targets.

  • Improved reachability analysis and test case generation for the following coverage targets:

    • Condition targets appearing after short-circuit operators

    • Relational operator boundary coverage targets

  • Improved reachability analysis and test case generation for the following Simulink and Stateflow features:

    • Enumerated types

    • Simulink mask parameters

  • Improved reachability analysis:

    • Mark most types of target as unreachable if they occur within unreachable conditional subsystems.

    • Consider limited output ranges of certain functions (e.g. Sqrt/Sin/Cos) when determining reachability of downstream targets.

24.2.2. Extend Signal Tracing Into Stateflow Charts#

The existing signal-tracing mechanism in Reactis has been extended to trace into and out of Stateflow diagrams. If a signal entering or exiting a Stateflow chart is highlighted, Reactis will highlight all occurrences of the corresponding Stateflow variable in the Stateflow chart. If a variable is clicked within a Stateflow chart, Reactis will highlight all other occurrences of that variable within the chart. If the highlighted variable is a chart input or output, the corresponding signal in Simulink will also be highlighted.

24.2.3. Configuration-Variable-Based Variant Selection for Variant Subsystems#

For Variant Subsystems with activation time Code compile, Startup, or Runtime, Reactis now lets you use configuration variables to select the active variant. This means that for Variant Subsystems, coverage of all variants can be achieved within a single test suite and without re-importing the model.

Furthermore, a new API function rsRsiCreateVariantConfigurationSets automatically imports the configurations within Simulink.VariantConfigurationData objects into Reactis. This enables Reactis Tester to cover all variant configurations defined within the objects. The import automatically creates configuration variables and configuration variable sets in Reactis that correspond to the Simulink variant configurations and their control variables.

24.2.4. Improvements to Coverage Tracking#

Reactis now tracks coverage for Configuration Variable Sets. Each set is shown in the Configuration Variables panel in the model hierarchy and colored according to whether it has been covered or not. A Configuration Variable Set is considered covered when at least one simulation step has been taken where the value of each configuration variable matches its constraint from the Configuration Variable Set.

Apart from improving the visibility of whether a set has actually been used during simulation, the new tracking also enables Reactis Tester to automatically create tests that cover each defined Configuration Variable Set.

24.2.6. Other Improvements#

Export RSI file items to CSV file

A new menu entry Tools > Export to CSV File in the RSI File Editor lets you create a CSV file containing a list of the current model’s inports, outports, configuration variables and test points including the data types and constraints for each item.

Improve display of fixed-point values in GUI

For data items of fixed-point type shown in the Watched Variable Panel and Test Suite Browser, you can now specify the number of digits shown after the decimal point. Specifying -1 will show exactly as many digits as necessary to accurately represent the fixed-point value given its slope.

Provide menu item to open model folder

A new menu entry File > Open Model Folder let you open a Windows Explorer window for the folder in which the current model is located. This reduces the steps necessary to open files created by Reactis in other tools.

24.3. Previous Major Release Dates#

Major releases of Reactis for Simulink prior to V2025.2 occurred on the following dates:

V2025.2

December 3, 2025

V2025

June 3, 2025

V2024.2

November 21, 2024

V2024

June 5, 2024

V2023.2

December 22, 2023

V2023

June 30, 2023

V2022.2

December 23, 2022

V2022

June 22, 2022

V2021.2

December 23, 2021

V2021

July 9, 2021

V2020.2

December 18, 2020

V2020

July 17, 2020

V2019.2

December 20, 2019

V2019

June 28, 2019

V2018.2

December 20, 2018

V2018

June 27, 2018

V2017.2

December 22, 2017

V2017

July 7, 2017

V2016.2

December 22, 2016

V2016

June 20, 2016

V2015.2

December 18, 2015

V2015

June 30, 2015

V2014.2

December 19, 2014

V2014

June 25, 2014

V2013.2

December 17, 2013

V2013

August 14, 2013

V2012.2

December 19, 2012

V2012

June 14, 2012

V2011.2

December 20, 2011

V2011

June 22, 2011

V2010.2

November 19, 2010

V2010

February 8, 2010

V2009.2

July 22, 2009

V2009

January 16, 2009

V2008

June 10, 2008

V2007

October 31, 2007

V2006.2

November 6, 2006

V2006

January 25, 2006

V2005

May 18, 2005

V2004.2

December 17, 2004

V2004

March 3, 2004

V2003.2

October 16, 2003

V2003

February 4, 2003

V2002

June 3, 2002