<< The unexpected active window | Setup and Exclude tabs >>

Creating a Pilot Scenario

Examining Pilot Run Results

5-23

Check to see if the UAW script is generated as a result of a timing problem. If it
is, set a delay interval for the appropriate action object in the application map.
For information about setting delay intervals for Pilot runs, see Specifying a Delay
Interval to Include in Generated Scripts on page 5-49.

Using Pilot Scenarios to Simulate User Action Sequences

After the AUT stabilizes, you can use Pilots to test interactions involving multiple
functional areas of the AUT. Among other things, you can test how the AUT
responds when functional areas are exercised in a sequence that a user is likely to
follow. A Pilot scenario

lets you simulate and test a user action sequence in

the AUT.

To create a scenario, you combine Pilots inserted at different functional regions of
the application map and arrange them in an ordered sequence. Each Pilot in the
sequence contributes a few steps to each script segment that the lead scenario Pilot
generates. The lead Pilot then builds the best script from the pool of script segments,
each of which contains steps in the sequence that you specify.

Creating a Pilot Scenario

To create a Pilot scenario:
1. Determine the first functional area of the AUT that you want the scenario to

test, and insert a Pilot at the corresponding location in the application map. This
is the

lead Pilot in the scenario.

2. Name the lead Pilot object in the application map, and then change settings on

the Setup, Stop Criteria, and Exclude tabs on the Pilot properties page.

3. Insert additional Pilots at application map locations corresponding to the other

functional areas that you want to add to the test sequence. To ensure that
TestFactory calculates accurate code coverage values for generated scripts, do
not combine Pilots that have access to any of the same controls.

NOTE: If a Pilot already exists at a map location where you want to begin a
scenario, insert a new lead Pilot anyway. Segregating Pilots helps to limit
confusion regarding the function of each.

NOTE: To avoid making the scenario too complicated, we recommend that
you include non-lead Pilots that are fairly simple. Avoid adding Pilots that
contain their own scenarios.