The mabl agent supports many of the most common web app interactions. If the test intent or plan involves an unsupported interaction type, the agent prompts you to add in steps manually.
This article outlines supported and unsupported web interactions for the mabl agent.
Supported interactions
The agent can perform the following interactions:
- Clicking on elements
- Selecting from a menu
- Selecting from a dropdown
- Entering text
- Selecting a date from a date picker
- Importing relevant flows
- Creating, using, and asserting on variables
- Searching via a search bar and select from results
- Scrolling
- Waiting for the page to settle
- Static wait steps
- Asserting on page visuals with visual assertions
- Asserting that an element is on the page and contains certain text
- Changing the URL
- Navigating to a new tab
- Email testing
Agent assertions
- HTML assertions - the agent prefers to use HTML element assertions whenever possible for for the speed of execution and reduced cost.
- Visual assertions - the agent uses visual assertions when validating multiple elements or the negation of an element (e.g. "error message is not present"). Visual assertions are also used if the validation involves an image/visual content or is generally more complex than asserting against the text of an element currently on the page.
Unsupported interactions
While the agent covers many common interactions, there are specific scenarios where manual steps are required, including the following:
- Creating new flows or loops
- Snippets
- Database queries
- API steps
- Conditional steps
- Asserting on hidden element attributes
- Double clicks
- Hover steps
- Drag and drop steps
- Accessibility checks
- Creating and asserting on cookies
- MFA logins
- PDF testing
- Scrolling within an element
- Custom finds with CSS or XPath