Use case
Checkout flow testing that shops like a real customer
Checkout bugs rarely look dramatic. A discount that applies twice, a postcode field that rejects Amsterdam, a total that's off by the shipping fee. They just quietly cost you orders until someone notices.
Write it the way you'd explain it to a new hire
This is a full checkout test. There's no selector in it, and nothing to update when your designer moves the coupon field to the other side of the page.
The agent reads the page the way a shopper does, finds the size picker and the pay button, and works out the clicks on its own.
- 1Accept cookies if a banner appears
- 2Search for "running shoes" and add the first pair in size 42 to the cart
- 3Apply discount code WELCOME10
- 4Check out as a guest with a German shipping address
- 5Pay with the test card 4242 4242 4242 4242
- 6Verify the order total equals item price minus 10% plus shipping, in euros
Where checkouts usually break
Money maths. Line prices, quantity changes, discount codes that stack when they shouldn't, a free-shipping threshold that's applied before the discount instead of after. The agent checks the number at the end against the rule you wrote, so a wrong total fails the run.
Forms that assume one country. Address fields that need a US-style state, phone validation that rejects a +49 number, a postcode format nobody tested. Run the same flow with addresses from each market you ship to.
Payment. Test cards should go through, declined cards should show an error a person can understand, and the confirmation page should actually confirm something.
Everything in the way. Cookie banners, newsletter pop-ups, a promo modal marketing added on Friday. A scripted test fails on these. The agent closes them and carries on, like a shopper would.
When it fails, you can see why
Every run is recorded. Next to the video you get the agent's notes for each step: what it was trying to do, what it clicked and whether the page did what it should. A failed checkout points to the step that broke, not to a selector that went missing.
Questions
- Do you place real orders?
- We'd suggest your payment provider's test mode on staging. On production, a run can stop right before the pay button.
- What happens when we redesign checkout?
- Usually nothing. The test says what the shopper wants to do, not where the buttons are, so moving things around doesn't break it.
- Can it test several markets?
- Yes. Run the same flow per country and check currency, tax and shipping for each. More on that in localization testing.
- Who writes the tests?
- We do, during the free 30-day pilot. After that it's €299/month to start, and you can write your own or keep us doing it.
Protect your most important user flows
We write and maintain tests for your core flows during a free 30-day pilot. No credit card. Plans start at €299/month after that.