Wait Until Step
We're all fine with "up to a 15 minute wait" for a table to open at our favorite restaurant, but if a table is available before the 15 minutes is up, wouldn't you prefer be seated earlier rather than continue waiting? Similarly, we don't necessarily want mabl to wait a full 20 seconds every time the test is run, but we don't want that test to fail either just because a step times out right before the element appears on the page.
When you see it 👀
Now you can tell mabl to wait up to 15 minutes for a specific element to be present on the page before proceeding to execute subsequent steps! It's not as static as the simple Wait Step that you're used to, and also not as rigid as using a CSS and xPath query to find the element. Even if your Wait Until Step times out before finding the target element, mabl will still use the information learned about the target element to expand the search criteria and retry finding the element a couple times.
Add a Wait Until Step to your test from the "More actions" menu.
Use the cursor button to select your target element.
Select the target element, then configure the element attribute(s) that mabl should wait for. Set the timeout for the maximum amount of time mabl should wait before attempting to auto-heal to a new target element on the page. If a recognizable ancestor element is available, you can also configure attributes of the ancestor for mabl to wait on as well!
What is an ancestor element?
For any step that interacts with something on the page, there is a target element that mabl will attempt to find to execute the step. This is the element being clicked, asserted on, hovered over, etc. In cases when this target element is difficult to identify on the page, mabl will also capture information about a recognizable ancestor element to serve as a guide post for finding the target element. With configurable finds, you control how mabl finds each of these elements by selecting the attributes on each (or on just one) to wait for.
Choose the element attributes mabl should look for while waiting.
See your new Wait Until Step appear in your trained test.
Automatic retries by default
All mabl steps that perform an action on an element include automatic retries by default. Consider running your tests without explicit wait steps before adding them, as they are generally not required.
If longer waits are required, consider configuring how mabl finds the element directly on the step itself through the link below.
help.mabl.com