File System Limitations
Automated Testing
Click the Rendezvous Configuration button to set up any rendezvous members.
File System Limitations
Deployment of the Virtual Testers results in the creation of an .spv deployment
script. This script contains file system commands, such as CHDIR. If you are
deploying the test to a target platform that does not support a file system, you must
edit the .spv script manually.
Editing the Deployment Script
The System Testing Supervisor actually runs a script, which is automatically
generated by configuring Virtual Testers and deploying Virtual Testers.
In some cases, you will need to manually edit the script. To do this, you first have to
generate an .spv deployment script in your workspace.
To generate a deployment script
1. In
the
Project Explorer, right-click a System Testing node.
2.
From the pop-up menu, select Generate Deployment Script.
3.
Enter a name for the generated script.
If you decide to manually maintain a deployment script, you must ensure that any
pathnames and other parameters remain up to date with the rest of the System
Testing node.
For information on the .spv script command language, please refer to the Test
RealTime Reference Manual.
Optimizing Execution Traces
Each Virtual Tester generates a trace file during its execution. This trace file is used to
generate the System Testing Report.
You may want to adapt the volume of traces generated at execution time. For
example, each Virtual Tester saves its execution traces in an internal buffer that you
can configure.
To optimize execution trace output, use the Execution Traces area in the Test Script
Compiler Settings dialog box.
·
By default, System Testing generates a normal trace file.
·
Select Time stamp only to generate traces for each scenario begin and end, all
events, and for error cases. This option also generates traces for each WAITTIL
and PRINT instruction. Use this option for load and performance testing, if you
expect a large quantity of execution traces and you want to store all timing data.
·
Select Block start/end only to generate traces for each scenario beginning and
end, all events, and for all error cases.
197
