26. Tester Additional Parameters#

This section describes the format of the additional parameters string argument to rsTester. Each version of rsTester in the different bindings of the API offers a string argument for specifying extra configuration options for a Reactis Tester run. The string may include one or more of the following flags. All are optional.



-a {0|1}

Turns input abstraction on (1) or off (0). Inputs abstraction usually improves the performance of Tester and should be left on (default). In rare cases, turning it off may improve coverage. If coverage problems are encountered with inputs abstraction on, it may be beneficial to take a test suite produced with abstraction on, pre-load it into Tester, turn abstraction off, and then run Tester again.

-g c1;c2;...;cn

Specify a list of coverage metrics that should be used to guide test suite generation. Possible values for c1, c2, … cn are the coverage metric names listed in Coverage Metric Names and assertion category names in Assertion Category Names.

-p preloadList

Specify a list of .rst files to preload. preloadList is of the form fName1={y|n};fName2={y|n};...;fNamei={y|n}. The y|n argument for each file specifies whether or not pruning of the preloaded suite should be allowed. The random and targeted phases will extend the preloaded tests. The preloaded test suite files will not be modified.

-q timeoutSeconds

Specify the number of seconds to generate tests. Tester will stop after either the timeout expires, all steps steps in the random or targeted phases have been executed, or full coverage is achieved for the model, whichever comes first. If -q is given and -t is not given then Tester will continue until either the timeout expires or full coverage is achieved.

-r numTests;numSteps

Specify the number of tests and steps in the random phase. The defaults are 25 tests of 40 steps each.

-s randomSeed

Initial seed for the random number generator.

-t stepsInTargetedPhase

stepsInTargetedPhase specifies the number of execution steps to take during the targeted phase of test generation. The default is 20,000 steps.