Excluding an Interaction Object
Developing and Working with the Application Map
Excluding an Interaction Object from Mapping
Because interaction objects are TestFactory objects, and not UI objects, you cannot
exclude one from mapping by modifying properties. If you want to exclude an
interaction object from mapping, you must use its shortcut menu.
To exclude an interaction object from mapping:
In the application map, right-click the interaction object, and then click
Exercise During Mapping on the shortcut menu.
The Exercise During Mapping command toggles the mapping availability status of
the interaction object.
If you want to include the interaction object in mapping sessions later, be sure to
reset its active status.
Using Interaction Objects to Map Alternative Paths in the AUT
A functional area of an application can lead to multiple states, depending on how a
user exercises the controls it contains. During application development, it is
important that you map each available path in the AUT.
If you run a Pilot to test a region of the AUT that is not fully mapped, the Pilot can
encounter controls it does not "expect" to see. If this happens, the Pilot generates
UAW (unexpected active window) scripts and can fail to generate a code-coverage
optimized best script. (For information about UAW scripts, see Examining Pilot Run
Results on page 5-12 and Viewing a UAW Script on page 5-19.)
You can use interaction objects to map all of the available paths in an area of the AUT.
Without interaction objects, you can only map one of the available paths in an area
of the user interface.