Reviewing and editing steps
Use the step editor to review a draft beside its video, change actions and targets, add checks, and save or approve a new version of a test.
You never have to edit a test, but when a step needs fixing, or you want to add a check, the step editor makes it a form, not code.
Open the editor
- On a test with a draft, press Steps (or Fix steps after a failed validation).
- On an approved test, press Edit (new version). This creates a draft copy; the approved version keeps running until the new one is approved.
The editor shows the original video beside the steps. Select a step's timestamp to jump to that moment in the video, which is the quickest way to check what really happened.
The parts of a step
Each step has an action and, depending on the action, a target and a value:
| Action | Target | Value |
|---|---|---|
| Go to page | Page address | |
| Click | Text on the button or link | |
| Type | Field label or placeholder | What to type |
| Choose option | Field label | Option to choose |
| Tick / Untick | Checkbox label | |
| Point at (hover) | Text on screen | |
| Press key | Field (optional) | Key, for example Enter |
| Scroll | Text to scroll to (optional) | |
| Wait for | Text to wait for | or load / networkidle |
| Drag | Text on the item to drag | Where to drop it |
Targets are written as the words you see on screen. ReplayQA finds the element that shows them, the way a person would. If the same words appear in several places, or an element has no text (an icon button, for example), press Change to pick a more specific way to find it: by accessible name and role, label, placeholder, test ID or, as a last resort, a CSS selector.
Adding checks
Checks make a test meaningful: they confirm the flow actually worked. Add them to any step:
| Check | Use it for |
|---|---|
| Text is shown / Text is not shown | "Order confirmed" appears, or an error message doesn't |
| Element says | A total, a name or a status has the expected text |
| Page address | You ended up on /orders/… |
| Element is | A button is enabled or disabled, or a box is checked |
| Number of matches | The cart has 3 items |
| Server response | A request returned success, for example 200 /api/orders |
| Looks the same as before | A region matches the screenshot from the first approved run |
One or two strong checks at the end beat many weak ones in the middle. "Order confirmed" plus the order total is usually enough for a checkout.
Saving, validating and approving
- Save draft keeps your changes without running anything.
- Try against environment chooses which site the draft is checked and validated against.
- Back on the test page, press Start under Repeat the video in a real browser to validate the draft. If it passes, it becomes the new approved version.
- Approve without validating is available for experienced users who are sure of a change. Validation is safer.
- Discard draft throws the draft away. The approved version, if any, is unaffected.
Versions
Every approved version is kept under Versions on the test page, with who created and approved it and why (AI generated, manual edit, suggested fix). Open any version to see exactly what it did.