Beyond a Logon Dialog Box
Using Interaction Objects to Guide the Application Mapper through the AUT
Using an Interaction Object to Map Beyond a Logon Dialog Box
If the AUT contains a logon dialog box that requires input such as a password or user
ID, then you must perform additional steps after the first mapping session so that the
Application Mapper can access more of the user interface. The following figure
shows the Classics Login dialog box and the resulting application map after mapping
to single-level depth for the first time.
To get from the logon box to the Classics window, a user must enter a user name in
the Full Name combo box, type a password in the Password text box, and then click
OK. Because TestFactory did not have the required string cases to pass to the combo
box and text box, the Classics window did not open after the Application Mapper
exercised the OK button. To map beyond a login dialog box such as this, you must
supply TestFactory with the necessary input to pass to the AUT, and specify the
correct order for exercising the controls involved. The most efficient way to do this
is to set up an interaction object.
To map beyond a login dialog box using an interaction object:
1. Map the AUT to single-level depth.
After mapping is completed, the application map contains the StartAUT object,
and the UI objects mapped for the logon dialog box and its child controls.
2. On the Insert toolbar, click Interaction Object.
UI object mapped for the Full Name combo box
Classics Login dialog box
Single-level depth application map of Classics
To open the Classics window, a
user must first enter a user
name and a password, and
then click OK.
UI object mapped for the Password text box