How it works
From a few lines of text to a video of your site, after every deploy. No test code to write or keep up to date.
- 1
Describe who uses your product
Add your types of users, like Customer, Seller and Admin. Each one gets a test account with its own inbox, so we can sign up, log in and read the emails your site sends.
- A fresh email address every run
- Or an existing account, with its password and 2FA
- Saved logins, so flows start where they should
- 2
Write your flows in plain words
One step per line: what the user does, and what they should see. Flows can depend on each other, like “approve the shop” before “buy something”. Import and export them as YAML.
flow: Post a job for free as: employer steps: - Open /jobs/new → the job form - Fill in title and place → each field accepts it - Publish → the job shows in search - Pay with the Stripe test card → the success page
- 3
We run them in a real browser
The first time, AI works out each step on your page and saves it. Next runs repeat the saved steps: fast and the same every time. If your page changed, it repairs the step and says so.
- Run by hand, after every deploy, or from an AI agent
- On a desktop browser, on a phone, or both
- A video of every flow and a screenshot of every step
- 4
See what broke, and what you do not test yet
A broken flow shows the step, the page, the error, the browser console and the failed calls to your server. Coverage lists every button and link on your site, and which ones no flow uses yet.
- One plain sentence: bug in the app or a step to reword
- Speed of every step and call over time
- Flaky flows flagged
What your staging needs
We test on your staging site, never on your live site, because flows sign up, post and pay like real users do.
- • A staging website (and API) we can reach
- • Emails sent for real, or to our inbox
- • Stripe in test mode, if you test payments
- • Our runner's address allowed by your login rate limits