background image
<< Inserting a Synchronization Point During Editing | Adding Comments During Recording >>
<< Inserting a Synchronization Point During Editing | Adding Comments During Recording >>
Scope of a Synchronization Point
Adding Features to Scripts
8-12
Release Times and Timeouts for Synchronization Points in Test Scripts
You cannot define minimum and maximum release times or timeout periods for
synchronization points that you insert into scripts (as you can for synchronization
points that you insert into suites). By default:
Virtual testers held at a script-based synchronization point are released
simultaneously.
There is no time limit to how long virtual testers can be held at the
synchronization point.
However, if a synchronization point in a suite has a release time range and timeout
period defined for it, the release times and timeout period apply to all
synchronization points of that same name--even if a synchronization point is
in a script.
Scope of a Synchronization Point
The scope of a synchronization point includes all scripts and all user groups that
reference a particular synchronization point name.
For example, suppose a suite contains the following user groups:
A Data Entry user group of 75 virtual testers. This user group runs a script
containing the synchronization point Before Query.
An Engineering user group of 10 virtual testers. This user group runs a different
script than the Data Entry groups runs. But this script also contains a
synchronization point named Before Query.
A Customer Service user group of 25 virtual testers. This user group runs a
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.