Step Management
Step types, conditions, grouping, and shared steps
Steps are created and edited using the visual form in the test editor. This page describes the step types and how conditions work. For how to add and edit steps, see Steps Overview.
Step Types
Individual Steps
A single action — click, navigate, type, assert, and so on. See Built-in Steps for the full action list, and Additional Steps for JavaScript and specialised actions.
Group Steps
A container that holds child steps. Groups appear as collapsible rows in the editor. Use them to organise related actions — a login sequence, a form-filling workflow — without creating a shared step.
Shared Steps
A reusable step stored in the library and referenced from one or more tests. See Shared Steps.
Step Conditions
Each step can carry a condition that determines whether it runs. Set it in the Run with condition section of the step editor.
| Condition type | Behaviour |
|---|---|
| Always run | Always runs |
| Skip step | Never runs |
| Custom condition | Runs a JavaScript expression; skips the step if it returns falsy |
| Element visibility | Checks whether an element is visible (or not visible) at the moment the step would execute |
| Element text | Checks whether an element's text matches a value |
Step Versioning
Changes to a test's steps are tracked through revisions. See Revisions for how to create a named snapshot and view historical step lists.