20. Revision History

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

Fig. 20.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 for C is labeled by a “V” followed by the four-digit year (e.g., V2020). Each label for an intra-year release includes a suffix consisting of a decimal point followed by a major release number; for example V2020.1, V2020.2, etc. will label the releases during 2020 that follow V2020.

Beta Releases

RSI often makes beta releases available to customers interested in evaluating the newest features of Reactis for C. Beta releases do not undergo as much testing as major releases do. By convention, beta releases have odd numbered major release numbers. For example, V2020.1, V2020.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:

• V2020.2.1 denotes the first patch release for V2020.2

• V2020.0.2 denotes the second patch release for V2020

20.1. V2026 (10 June 2026)

V2026 focuses on improved testing flexibility and AUTOSAR whole-component testing. Key additions include pragma-based coverage control and whole-component AUTOSAR testing. The V2026 release of Reactis for C includes all bug fixes that were included in patch release V2025.0.1, plus the following new features.

20.1.1. Disable Target Generation for a Section of Code

Reactis for C tracks how thoroughly tests exercise your code using a collection of coverage metrics, including statement coverage, decision coverage, condition coverage, MC/DC coverage and others. For each metric, a set of coverage targets are identified within your code. Reactis Simulator then tracks whether each target has been exercised and Reactis Tester attempts to generate tests that maximize the number of targets exercised.

While you typically want to test your entire program, sometimes you may wish to focus on one part of your code and not on others. To facilitate such focused testing, V2026 introduces a new C pragma to disable target generation for a section of code. #pragma REACTIS coverage off stops target creation for all lines which follow, until a line containing #pragma REACTIS coverage on is reached. There is no need to modify your source files, since these pragmas can be added as instrumentation code. This lets you precisely target the important sections of your code, while ignoring irrelevant parts. The new pragmas are especially useful for testing code that accesses legacy code, external libraries, or third-party code not under your control.

20.1.2. Whole-Component AUTOSAR Testing

V2025 introduced an AUTOSAR import wizard that, given a set of ARXML files describing an AUTOSAR component, generates a minimal RTE, build file, and harness necessary to test a single runnable of the component in Reactis for C.

V2026 extends the import tool to facilitate testing a whole component, i.e. all runnables of the component together. When importing a component with multiple runnables, Reactis for C automatically generates a scheduler that triggers each runnable as specified in the AUTOSAR component.

Previously, only single runnables could be tested in isolation. V2026 now enables integrated testing of all runnables with automatic scheduler generation.

20.1.3. Store Compiler-Generated Files in a Separate Folder

V2026 offers a new global option in the C Code tab of File > Global Settings… that lets you configure Reactis for C to store compiler-generated files in a separate folder. You can place all files in a subfolder of the folder containing the build (.rsm) file, or select a single folder to contain all compiler-generated files. This makes it easy to keep track of compiler-generated files, and delete them when they are no longer needed.

20.1.4. Other Improvements

Data dictionary variable names are now automatically matched during harness import.

When importing a Reactis for C test harness from a .rsi file, names which originate from a Simulink data dictionary (.sldd) file are now automatically matched to variables in the C code with the same name. This eliminates the need to manually match data dictionary variables.

Open the build file folder in Windows Explorer from the File menu.

A new menu choice File > Open Build File Folder opens the folder containing the currently open build file in Windows Explorer. This is useful when you need to access files outside of Reactis.

Version	Release Date
V2025	December 3, 2025
V2024	June 5, 2024
V2023	December 22, 2023
V2022	June 22, 2022
V2021	July 9, 2021
V2020	December 18, 2020
V2019	June 14, 2019
V2018	February 9, 2018
V2016	October 21, 2016
V2015	November 18, 2015
V2014	April 10, 2014
V2011	March 21, 2011