The Test Creation 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 Test Creation 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
- Asserting on page visuals with GenAI Assertions*
- Asserting that an element is on the page and contains certain text*
*The Test Creation Agent prefers to use element assertions when possible for the speed of execution and reduced cost. The agent uses GenAI assertions against the page viewport if the assertion involves multiple elements, the negation of an element (e.g. "error message is not present"), requires the validation of an image or other 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
- Hover steps
- Navigating to a new tab
- Changing the URL
- Static wait steps
- Drag and drop steps
- Accessibility checks
- Creating and asserting on cookies
- MFA logins
- Email testing
- PDF testing
- Scrolling within an element
- Custom finds with CSS or XPath