To make test authoring sessions more resilient and reduce the need for manual intervention, we're happy to share a whole new range of supported step types and authoring patterns for the mabl agent in browser tests.
Read on to learn more about what's new:
Accessibility and test logic
- Accessibility checks - insert an axe-based accessibility check at any point in a test, optionally scoped by severity, WCAG tag, or disabled rules.
- Conditional logic - add IF, ELSE IF, and ELSE blocks so tests can produce more realistic test flows that handle optional UI stages or variable outcomes without requiring manual step editing.
- MFA logins - enter a temporary code from a test's credential during an MFA prompt, with no manual handoff required. A new on-demand mfa-authentication skills guides the agent on when and how to use this capability.
Browser and page control
- URL assertions - verify that navigation leads to the correct destination. Previously the agent had to skip or work around URL verification requests.
- Set viewport - use natural language prompts to set the browser width and height to validate responsive-layout scenarios
- Refresh page - test states that should persist after a refresh, or clear a transient UI state mid-test
Cookie management
- Set cookie - create or overwrite a named cookie with a specific value, domain, path, expiry, and security flags. Useful for injecting auth tokens or feature flags without going through the UI.
- Remove cookie - delete a specific named cookie.
- Clear all cookies - wipe the entire cookie jar for the current session. Useful for testing signed-out states or fresh-session flows.
- Cookie assertions - assert on browser cookie properties, including value, domain, path, expiry, http_only flag and secure flag. Useful for verifying session cookies were set after login, consent cookies captured user choices, or feature-flag cookies are present.
Inline API steps
- API steps - make GET, POST, PUT, PATCH, DELETE, HEAD, or OPTIONS calls inside a browser test, with header and body support, basic and bearer auth, response validations, and variable extraction for use in subsequent steps
PDF & file Testing
- Download and verify files - author a file download step and assert on its name, size, MIME type, and contents.
- Open and verify PDF content - open a PDF in the mabl PDF viewer and assert on its content. Useful for testing document generation flows where a PDF is displayed inline in the browser.
Custom CSS and XPath
- Custom find steps - if the default screenshot-based visual find isn't enough, you can provide an explicit CSS or XPath selector for click, enter text, hover, assert element, and variable extraction steps.The selector is used verbatim with no AI heuristic applied on top. This capability is opt-in: when custom find is not provided, the existing visual find behavior is unchanged.