background image
<< Use of datapools in test scripts | Changing the Way Random Numbers Are Generated >>
<< Use of datapools in test scripts | Changing the Way Random Numbers Are Generated >>

Changing the Number of Start Test Scripts

Implementing Tests as Suites
109
Changing the Number of Start Test Scripts
If you are starting virtual testers in groups, TestManager lets you specify the number
of test scripts that the group of virtual testers must complete successfully before the
next group starts. You may need to do this to control the maximum number of virtual
testers that log on to a system at a given time.
For example, assume the Data Entry user group contains 100 virtual testers. Each
virtual tester runs a Login test script and then selects three test scripts in a random
order: Add New Record, Modify Record, and Delete Record. You have changed the
runtime settings so that the 100 virtual testers are not starting all at once; instead, they
are starting in groups of 25.
If you set the number of start scripts to one, the second group of 25 starts when each
virtual tester in the first group of 25 completes the Login test script. The third group of
25 starts when each virtual tester in the second group has completed the Login test
script, and so on.
To change the number of start test scripts:
s
Open a suite, and then click
Suite > Edit Settings
.
Limiting the Number of Test Scripts
TestManager lets you limit the number of test scripts that virtual testers can run
without having to remove any test scripts from the user group. You can test the suite
run in an abbreviated form to ensure that all suite items are working correctly.
For example, limit the number of test scripts to:
s
Ensure that a sequence can run for a limited time before you repeat it indefinitely
in a suite. Assume that your suite has a sequence of eight test scripts that repeats
indefinitely. To ensure that virtual testers are able to start, execute, and complete
the sequence twice, insert a sequential selector before the test scripts, and then set
Script Limits
to 16.
s
Temporarily disable a user or computer group without deleting it from the suite.
By setting
Script Limits
to 0 for the group, you disable it. (You can also disable a
fixed group by setting the number of virtual testers to 0.)
s
Check that a datapool works correctly. For example, assume that a virtual tester
enters records into a database 100 times. To check that the virtual tester enters a
unique record, set
Script Limits
to 2. If a virtual tester enters the same record twice,
the run fails.
To limit the number of test scripts that a suite runs:
s
Open a suite, and then click
Suite > Edit Settings
.