Repeating tests in a schedule
By adding a loop to a schedule, you can repeat a test for
a number of iterations and set the rate for running a test. If the
loop contains a synchronization point, the synchronization point is
released after the first iteration of the loop and stays released
for all further iterations.
About this task
A schedule that contains only user groups and tests runs each test in a user group sequentially. Loops provide more sophisticated control than running a simple sequence of consecutive tests.
You
can set a loop within a schedule or a test. The following table shows
the advantages of both methods:
Loop location | Results |
---|---|
Schedule | Loops in schedules are easy to locate and modify. Loops in schedules close the server connection at the end of each iteration and reopen it at the beginning of the next iteration. This action models the behavior of a user closing and reopening a browser. Use this method to run a test at a set rate. For more information, see Running tests at a set rate. |
Test | Loops in tests can be more granular, and thus
provide a higher level of control. Loops in tests reuse the server connection during each loop iteration. Use this method, with loops that have high iteration counts, to stress test a server. |
Procedure
To add a loop to a schedule: