Communication Between Virtual Testers

System Testing for C

Virtual Testers can communicate between themselves with simple messages by using the INTERSEND and INTERRECV statements. Virtual Tester messages can be either an integer or a text string.

For information about the INTERSEND and INTERRECV statements, please refer to the System Testing Script Language section in the Studio Reference pages of the help.

For these statements to be active, you must enable On-the-fly Runtime Tracing in the Configuration Settings.

To enable Virtual Tester communication:

In the Project Explorer, select the System Testing test node, and click Settings.
In the Configuration Settings dialog box, select System Testing and Target Deployment Port for System Testing.
Set Enable On-the-fly Runtime Tracing to Yes and click OK.

Identifier

For message delivery purposes, each Virtual Testers carries a unique identifier. The virtual tester identifier is constructed with the following rules:

If the Virtual Tester is run as an instance named <instance>:

If the Virtual Tester is running in multi-threaded mode, with its entry point in <function>:

<function_name>_<occid>

In any other case, the identifier uses the .rio file name:

By default the occurrence identification number <occid> for each Virtual Tester is 0, but you can set different <occid> values in the Virtual Tester Deployment dialog box.

There must never be two Virtual Testers at the same time with the same identifier. If an INTERSEND message cannot be delivered because of an ambiguous identifier, the System Testing supervisor returns an error message.