Interaction between navigate and popup-handling actions
This topic describes a possible issue that may arise when you use the navigate built-in action in combination with popup-handling actions
It is very common that you’d like to navigate to a specified URL either within an existing Chrome window, or from a newly launched instance of Chrome. In both of these cases, if your test calls popup-handling action(s) right after the navigate built-in action, the popup-handler queue may apply the previous page session, instead of the target URL page session. Consequently, the popup-handler queue will not be handled properly on the target URL.
Because you are already aware of the control triggering a popup window on the target URL, to avoid this problem, it is highly recommended that your test procedure waits for the control until it is available before invoking its popup-handling action. In this manner, you are assured that the popup-handling action, and all subsequent ones, apply to the target URL page session.
Scenario
You want to navigate to a shopping cart page, for example, www.shoppingcart.com, from an existing instance of Chrome running on Android. On the target page, your test will click a button, Delete this item, to remove an item from your cart:
- Upon clicking the button, a confirmation popup is expected to appear with the message Do you want to delete this item?. Two buttons, OK and Cancel, are displayed.
- Your test clicks the OK button.
The optimum test procedure should be something like the following:
location window handle
navigate www.shoppingcart.com scrumboard
window control timeout(second)
wait for control home delete this item 20
button
click on next popup OK
window control
click home delete this item
wait for control is used to ensure that the control triggering a confirmation popup is available within 20 seconds before click on next popup is placed into the current popup-handler queue of the shopping cart page