background image
<< The virtual testers in the Accounting user group wait | Scope of a Synchronization Point >>
<< The virtual testers in the Accounting user group wait | Scope of a Synchronization Point >>

Why Use Synchronization Points?

Inserting Other Items into a Suite
Although a virtual tester that reaches a synchronization point after a time-out is not
held, the virtual tester is delayed at that synchronization point. So, for example, if the
time-out period is reached, and the restart time is 1 second and the Maximum time is
4 seconds, a virtual tester is delayed between 1 and 4 seconds.
The default time-out is 0, which means that there is no time-out. Setting a time-out is
useful because one virtual tester might encounter a problem and might never reach
the synchronization point. When you set a time, you do not hold up other virtual
testers because of a problem with one virtual tester.
A suite or test script can have multiple synchronization points, each with a
unique name. A given synchronization point name can be referenced in multiple test
scripts and/or suites.
Why Use Synchronization Points?
By synchronizing virtual testers to perform the same activity at the same time, you
can make that activity occur at some particular point of interest in your
test--for example, when the application sends a query to the server.
Synchronization points inserted into test scripts are used in conjunction with timers to
determine the effect of varying virtual tester load on the timed activity. For example,
to simulate the effect of virtual tester load on data retrieval:
While recording the test script (named VU1 in this example) that submits the
query and displays the result, perform the following actions:
Insert a synchronization point named
into the test script.
Start a block.
The block times the transaction you are about to perform. The block also
associates the block and timer names with the name of the emulation command
that performs the transaction.
Submit the query and wait for the results to be displayed.
Stop the block.
While recording the test script that provides the load, insert another
synchronization point just before you begin to record the task that provides the
load. For example, just before you click to submit an order form, add a
synchronization point. Name this test script VU2.
Add VU1 and VU2 to a suite.