background image
<< Inserting a Pilot | Settings on the Stop Criteria Tab >>
<< Inserting a Pilot | Settings on the Stop Criteria Tab >>

Application map levels

Setting Up and Running Pilots
5-5
Just as you can map the AUT in increments, you can also test the AUT in
increments. In full-depth testing, the Pilot drives to the base state (the UI object
at which you inserted the Pilot) and from there, exercises every control it
encounters at all levels of the AUT. In single-level depth testing, the Pilot drives
to the base state and exercises the control it represents, but does not exercise
other controls that are exposed.
2. To let the Pilot explore its area of the application map to full depth, under
Test depth, leave Full selected. To limit Pilot exploration to the top level of
UI objects that it encounters in the application map, click Single level.
TestFactory passes the value specified in the Route number box to the random
number generator to determine the starting path that the Pilot takes to
generate scripts.
3. If you have run this Pilot before, and you want it to take a different starting path
on the next run, under Options, type a new number between 1 and 99 in the
Route number box. The route number you specify to change the run path is not
important, as long as it is different than the previous one.
4. To generate just a UI script, and prevent the Pilot from generating other kinds
of scripts:
a. Under Options, select the Generate UI script only check box.
After you select the check box, the UI Script button replaces the Start
button at the bottom of the Pilot properties page.
b. To start the Pilot run and quickly generate a UI script, click UI Script.
5. If the Use Test Lab check box is selected, clear it.
To make external resources available to the AUT during testing, use the boxes
under Support scripts. For example, to initialize a database of customer names
and give the AUT access to it, you can create a Robot script that initializes the
database, and then specify that script as a startup script for the Pilot run. You can
also create a Robot support script that sets persistent defaults in the AUT. To
restore the system to its previous state after testing, create a cleanup script in
Robot, and then specify it as a cleanup script in the Setup tab.
6. To specify support scripts for a Pilot run:
a. Under Support scripts, click Browse next to the Startup box, and then
locate and select a Robot script that brings the system to the state
appropriate for the Pilot run.