background image
<< The Classics Login application map | The Incomplete Order message box >>
<< The Classics Login application map | The Incomplete Order message box >>

Mapping Alternative Paths in an AUT

Using Interaction Objects to Guide the Application Mapper through the AUT
4-39
Mapping Alternative Paths in an AUT
The following figure shows the Make An Order dialog box in the Classics sample
application. To order a selected album, a user types a credit card number in the Card
Number box, types the expiration date for the card in the Expiration Date box, and
then clicks Place Order.
After a user correctly submits an order, Classics displays the Order Confirmation
message. If the user clicks Place Order without first completing the Card Number
and Expiration Date boxes, Classics displays the Incomplete Order message. To test
this area of Classics, you must first map both of these paths in the user interface.
To map alternative paths in an area of the AUT, start by mapping the default path that
the Application Mapper takes if you do not specify input for controls in the AUT.
Next, insert and set up an interaction object for each alternative path that a user can
take, starting from a specific control (the last control involved in an interaction that
exposes unmapped user interface).
To place an order
for a selected
item, a user must
type information
in these text
boxes, and then
click Place Order.