Virtual Tester

Syntax

<virtual tester> [-INSTANCE=<instance>] [-OCCID=<id_number>] [-RIO=<trace_file>]

Description

Virtual testers are multiple contextual incarnations of a single .pts System Testing test script.

One virtual tester can be deployed simultaneously on one or several targets, with different test configurations. A same virtual tester can also have multiple clones on the same target host machine.

Deployment of virtual testers is controlled by either the GUI or a System Testing .spv supervisor script when running in the command line interface. Do not edit .spv scripts when using the GUI.

System Testing for C generates virtual testers from a test script according to the declared instances.

Note   A System Testing Agent for C must be installed and running on each target host before deploying virtual testers to those targets.

Following the execution architecture and constraints needed to comply, the System Testing Script Compiler provides several ways to generate the virtual testers.

Options

Virtual testers can take the following command line options:

-INSTANCE=<instance>

If the .pts test script contains DECLARE_INSTANCE instructions, this option specifies which behavioral instance the virtual tester is to initiate. By default, the virtual tester generates all behaviors contained in the test script, but on execution, only one instance is adopted.

If no instances are selected even though instances do exist in the test script, the virtual tester stops with a fatal error message.

 

-RIO=<trace_file>

This syntax specifies the name of the execution trace file to be generated by the virtual tester.

If you do not define a trace filename, the name <virtual tester>.rio will be used.

 

-OCCID=<occurrence_id_number>

This allows you to specify the occurrence identification number to use in the virtual tester identifier when using communication between virtual testers. See the INTERSEND and INTERRECV statements for more information.

 

-STUDIO_LOG

This option is for internal usage only.