December 23, 2021
Dear Reactis User:
We are pleased to announce the availability of:
The Reactis V2021.2 release includes all bug fixes from patch releases V2021.0.1 through V2021.0.2 plus the following new features.
Reactis V2021.2 introduces interval coverage, a new metric which is based on a set of user-defined intervals for each harness outport and test point in a model. For every specified interval, interval coverage tracks whether or not a value which lies within that interval has been produced at least once by the corresponding outport/test point. Intervals can be defined in a graphical editor in the Reactis GUI or added via the the Reactis API. For each interval, Reactis will track the test and step in which the value of the test point or output port first fell within the interval.
In addition to range intervals specified by min/max boundaries, a special initial value interval y0 enables tracking whether the value of the tracked item has ever changed from its initial value.
Reactis can be configured to automatically create the not initial value interval target ~y0 for each harness output in order to track whether each output has changed from its initial value. This setting can be configured by selecting Edit>Coverage Metrics, then enabling Track whether outputs have changed from initial value.
For any harness input, Reactis supports assigning a constraint that limits the set of values Reactis generates for the input during test generation or random simulation. For example, a constraint can specify a range consisting of a minimum and maximum value. Prior to V2021.2, for inputs of type double or single, a range could also include a step size (aka resolution). For each element of the range with resolution, the difference between the value and the minimum value is an integer multiple of the step size. For example, the constraint double [1.0:2.0:5.0] specifies a minimum of 1.0, a step size of 2.0, and maximum 5.0 as a shorthand for the the set 1.0, 3.0, 5.0. Reactis V2021.2 extends this facility to support step constraints for inputs with integer types.
In a test suite generated by Reactis Tester, if two or more tests share a common prefix of test steps, then the common steps are only stored once instead of being duplicated. Starting in V2021.2, Reactis Simulator makes use of this prefix sharing by only executing common prefixes once. Depending on the test structure and especially for large models, this can significantly reduce the time it takes to execute Tester-generated test suites or generate reports in Reactis Simulator.
Covering targets that require a counter in the model to count up or down by a certain number of steps is a hard problem for automatic test case generators in general. Reactis has always provided a way for users to tag such counters/timers (see section 9.3.3 in the Reactis User's Guide). Tagging a counter allowed Reactis to observe its value and focus on simulation steps that increase the count.
Reactis V2021.2 improves on this feature by analyzing the conditions that lead to the timer to increase. Reactis traces the relevant signals to the top-level inputs of the model and attempts to actively produce input values that will increase the timer.
The V2021.2 release of Reactis Model Inspector includes the following new features.
The following bugs were fixed since V2021.0.1:
The following bugs were fixed since V2020.2.3:
You may download the patches or full installers from the Reactis User Pages.
Best Regards,
The Reactis Team