Web steps
Every step available in the web test builder, organized like the step palette.
Web tests are built from the steps below. The groups match the categories of the Add step palette in the test builder, so what you see here is what you see in the product.
Interactions
| Step | What it does |
|---|---|
| Click | Click an element located by AI description or selector |
| Double click | Two rapid clicks, for edit modes and list items |
| Right click | Open an element's context menu |
| Hover | Reveal menus, tooltips, and hover states |
| Upload file | Feed a file to a file input |
| Press keys | Send keyboard keys and shortcuts |
| Fill input | Type text, variables, or generated data into a field |
| Scroll | Bring an element into view |
Email & SMS
| Step | What it does |
|---|---|
| Get sms code | Wait for an SMS and extract its code into a variable |
| Get mail | Verify an email arrives in a test mailbox |
| Get email code | Wait for an email and extract its code into a variable |
| Get email link | Wait for an email and extract a link into a variable |
Verifications
| Step | What it does |
|---|---|
| Verify element | Check an element is (or is not) displayed, clickable, enabled, or present |
| Verify Spell Check (AI) | Have the AI proofread the visible text of the page |
| Verify with AI | Assert anything about the screen in plain language |
Navigation
| Step | What it does |
|---|---|
| Switch window | Continue the test in another tab or window |
| Navigate to URL | Load a URL, with optional loading-time checks |
Wait for
| Step | What it does |
|---|---|
| Wait for delay | Pause for a fixed duration |
Others
| Step | What it does |
|---|---|
| API Call | Send an HTTP request and assert on the response |
| Custom step | Run your own JavaScript |
| Set variable | Store a value for later steps |
| Extract value | Read an element's text or value into a variable |
Four legacy steps no longer appear in the palette but keep running in existing tests: Assert displayed, Assert not displayed, Set checkbox, and Select.
Common step settings
Every step shares a few settings, shown in the step's side panel in the builder:
- Ignore error on this step (
ignore_errors): the run continues with the next step even if this one fails. - Skip during run (
disabled): the step stays in the scenario but is not executed. - Custom capabilities (
use_capabilities,capabilities): fine-tune or override the execution behavior for this step only.
Steps that target an element also share the AI settings: a plain-language description, an optional manual selector, and an AI strategy (inherit, smart, or always) that decides when the AI locates the element versus the saved selector. See AI selectors.
Step checks
Interactions and navigation steps can carry checks, evaluated right after the step runs:
- URL: the page address is exactly, contains, starts with, or ends with a value.
- Loading time: on the starting page step, the page load stays under a threshold.
- Step duration: the step itself stays under a threshold.
The Checks tab holds them in two groups: Success conditions, which fail the step when they are not met, and Warnings, which flag the run without failing it. Each group has its own and / or logic. Expected and actual values land in the run results.
See Success, warning, failed for what a warning does to the execution and to the monitor behind it.
From results to analytics
Each step records its timing, status, screenshots, check results, and any variables it created. At the test level, every run feeds the test measurement used by Analytics: duration, success/warning/failure counters, and on failure, which step type broke the run. Custom metrics created in steps flow to the same place.
What's next?
Last updated on