Automated Testing and Validation with Reactis®

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

Appendix B  Revision History

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

Figure B.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, for example V2011. Each label for an intra-year release includes a suffix consisting of a decimal point followed by a major release number; for example V2011.1, V2011.2, etc. will label the releases during 2011 that follow V2011.
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, V2011.1, V2011.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. Some examples clarify the scheme:
V2011.1.2denotesthe second patch release for V2011.1
V2011.0.1denotesthe first patch release for V2011

B.1  V2016 (21 October 2016)

The following general features have been added since the previous release:

  • The Reactis for C API has been greatly expanded and improved. Operations such as creating build files and harness libraries are now supported. The new Reactis for C API is designed to easily be used in combination with the Reactis for Simulink API to perform automated back-to-back testing.
  • Test harnesses now include an initialization function, which eliminates the need for wrapper code in many cases.
  • Reactis for C now includes a library of scripts for accessing the Reactis for C API from within MATLAB.
  • Support for C code which perform fixed point calculations has been added to the Reactis Harness Editor. Test harnesses can be configured to convert between real-world values and the fixed point representation used in the C code.
  • Settings which control the rounding mode and overflow behavior when a harness value is converted to/from a C code value has been added to the Reactis Harness Editor.
  • Stub file generation has been improved. Stub files now include all the type declarations required to compile. Stubs are not generated for unneeded functions and variables.
  • The Reactis Build File Editorhas been streamlined to make the use of .rsm libraries easier.
  • The number of output differences for which details are printed in a test execution report can now be capped, which prevents the reports from becoming excessively long when there are many output differences.
  • The Reactis for C Compiler now supports GNU statement expressions.
  • The Reactis for C Compiler no longer generates irrelevant error messages for variables and code which are not used by the current test harness.
  • The Reactis for C Compiler now produces a warning instead of a syntax error when compiling code which contains GNU asm directives.
  • The Reactis for C Preprocessor now allows the use of a macro as an argument to a #include directive.

B.2  Previous Major Release Dates

Major releases of Reactis for C prior to V2016 have occurred on the following dates:

VersionRelease Date