Writing good test steps
This is the single highest-leverage skill in the product. The engine is interpreting your words, so precision pays for itself immediately.
Name what you can see
Quote the visible label of the control exactly as it appears on screen.
| Instead of | Write |
|---|---|
| Click the button | Click the 'Continue to payment' button |
| Scroll down | Scroll down to the 'Order Summary' section |
| Verify the balance | Verify the account balance shows $1,234.56 |
| Click Delete | Click Delete for the 'Flight' project |
Say where, when it matters
If a label appears more than once, add its location: "Click the 'Add to Cart' button on the 'Roaster's Choice Box' panel". Product pages with carousels and related-item strips are the classic case — the same label can appear five times.
One idea per step, mostly
Compound steps work — "Enter the promo code BREW10 in the 'Promo Code' field, then click 'Apply'" — but a step doing six things is harder for the engine and much harder for you to diagnose when it fails. Split at natural boundaries.
Waiting
Steps beginning with "wait" are handled without an AI call:
Wait 10 seconds— an exact pause.Wait for the 'Order Confirmed' message to appear— polls until the text is present, then fails loudly if it never arrives.Wait for the page to load— waits for the page to settle.
The ambiguity warnings
The product checks every step as it runs and flags wording that could be read more than one way — pronouns without a clear antecedent, generic click targets, missing locations. These never block a run. They appear on the step in the results with a suggested rewrite you can apply with one click.