<< Scope of a Synchronization Point | Initialize Database test script >>

Using Events and Dependencies to Coordinate Execution

293

A Customer Service user group of 25 virtual testers. This user group runs a test
script that contains no synchronization points. However, the user group does have
a synchronization point defined for it. This synchronization point is also named
Before Query.

At suite runtime, TestManager releases the virtual testers held at the Before
Query synchronization point when all 110 virtual testers arrive at their respective
synchronization points.

Using Events and Dependencies to Coordinate Execution

An event is a mechanism that coordinates the way items are run in a suite. For
example, you are running a suite that contains 100 virtual testers that access a
database. You want the first virtual tester to initialize the database and the other 99
virtual testers to wait until the initialization is complete. To do this, you could set a
dependency on the initialization event, which blocks the 99 virtual testers until the event
(the first virtual tester initializes the database) occurs.

You can have multiple events in a suite. Although only one item in a suite can set an
event, many items can depend on the event.

Note:

Events and dependencies require only that actions occur--not necessarily that

they complete successfully. If parts of your suite require that actions not only occur
but also complete successfully, use a precondition on a test case, test script, or suite.
For more information about preconditions set on items within suites, see Setting a
Precondition Within a Suite on page 269.