24 / 26 Engineering and QA · Example
Test a web app
Your users write test steps in plain English, and each run follows them in a real browser and screenshots every step.
- Who it’s for
- Testing tools whose users would rather write “add two items and check out” than maintain selectors.
- Why it’s hard
- Scripted tests break when a button moves or a label changes. A step only passed if the page afterwards says so, and someone has to read it.
- You get back
-
- A pass or fail for every step, with its screenshot
- For each failure, what the page said instead
- Changes your user accepted, noted in the report
Every run starts on a new computer, so no sign-in or half-full basket is left over from the last one.
How it runs, in your product’s code
Your user picks the plans, and each gets a fresh computer. After every step it’s told what changed on the page, and decides from that whether the step passed. When the page says something the plan didn’t expect, like “Order received” where step 9 wants “Order placed”, the run stops and asks your user: bug, or expected change? The report lists each step as passed or failed, with its screenshot.