background image
<< Execution Order | Controlling How a Suite Terminates >>
<< Execution Order | Controlling How a Suite Terminates >>

Time Information

Chapter 5 - Executing Tests
Suites that run in a custom order require you to select specific user
groups or virtual testers to run. Apply a custom run order to fixed user groups
Running user groups in a custom order is useful for troubleshooting. For example, if a
test script does not work and that test script is used only by the Accounting group,
run that group only.
To create a custom run order, click
in the Runtime Settings dialog box.
You can also temporarily disable a fixed user group by selecting it, clicking
Edit > Run
, and then setting
User Count
to 0.
You can run fixed virtual testers first, thus running fixed user groups before the
scalable user groups, regardless of the execution order. If your user groups are all
fixed, specifying a run order has no effect.
Time Information
This option controls timing information such as:
The maximum amount of time the run should take. A value of 0 imposes no time
The maximum number of seconds for all virtual testers to confirm that they
completed initializing. If you have changed the number of start test scripts, make
sure that you set this time high enough.
Suppressing timing delays. Any calls to TSS think times will delay 0 seconds (no
delay), thus running the suite very quickly. This choice is useful if you are testing a
suite to see whether it runs correctly and you are not interested in the timing
delays. However, this creates a maximum workload on the server, Local, and
Agent computers.
Do not suppress timing delays if you are running a large number of virtual testers.
Initializing time stamps for each test script, which indicates whether time stamps
are carried over from script to script or are reinitialized with each script.
This option sets the number to feed to the random number generator.
TestManager uses a specified seed to generate the random numbers for selectors and
shared access in datapools.