Promo codes
The agent types the code, applies it and checks the discounted total in the same run.
[02] Checkout under test
Checkout written
in plain language
Agents add a product, apply the promo code and pay with test-mode details. Each step is a sentence you can read.
A checkout flow in five steps
A login, three actions and one assert, each written as a sentence. The run panel keeps every result next to the steps that produced it.
Test payments
Payment steps run against your provider in test mode with the details you put in the step.
Order confirmation
An assert step checks the confirmation page, so a run only passes when the order goes through.
Mobile checkout
The same flow runs on a mobile viewport, so the phone checkout gets tested as well.
Watch agents check out on your store
Add your store URL, describe the checkout in plain language and read the first result.
[03] Promo codes and payments +
Promo codes and payments, every run
Runs on Production and Staging cover promo codes, saved cards, guest checkout and refunds. Failed runs stand out in Results, with the failing step and its screenshots.
Failures
caught
A failed checkout shows up as a Failed row, with the step where the agent got stuck.
Live and staging stores
Point the same tests at the live store or a staging copy and compare the results.
Shopify, WooCommerce, Stripe
Agents drive whatever your storefront renders in the browser and pay through the provider's checkout.
Scheduled checkout checks
Scheduled runs test the checkout against Production and post the results to Slack.
Guest checkout and refunds
Runs cover guest checkout, saved cards and refunds alongside the promo flows.
[04] Explore the platform +
Run at every step of shipping
The same tests run on every pull request, from your CI job, on a schedule against Production, or by hand. Every run lands in one Results table.
[04] Proof
Teams that ship storefronts
with agents on the flows
Automatic auth with test accounts was the blocker that killed our earlier QA attempts, and now we monitor our logged-in dashboard continuously without thinking about it.
Witold de La Chapelle
Co-Founder and CTO, Standout
FAQ
Frequently asked questions
Does it work with our platform?
Agents test the rendered storefront in a real browser. Shopify, WooCommerce, Magento, BigCommerce and custom or headless stores can use the same plain-language approach: add a product, apply a code, check out and verify the result.
Can it test on mobile viewports?
Yes. Configure a mobile viewport for the test and run the same shopping flow at that size. The recording shows how the cart, address form and checkout behave on the smaller screen.
Can we run before peak events like Black Friday?
Yes. Run the checkout tests against your staging or preview store before the campaign goes live. Add scheduled checks on Production during the event to catch changes in the storefront, promo codes or payment flow.
Can it test guest checkout and refunds?
Yes. Describe the guest checkout or refund flow in a saved test and point it at the appropriate environment. Use a staging store, test-mode payments and dedicated test orders for flows that create orders or issue refunds.
Can it test Stripe, PayPal or Klarna checkouts in test mode?
Yes. Configure the provider's test or sandbox mode and include the payment details the agent should use in the test steps. Agents follow the checkout in a real browser and verify the order confirmation and total.
What about discount codes and promo flows?
A test can enter a promo code, apply it, verify the discounted cart total and shipping, then check the order summary and confirmation. Keep the code and expected total in the plain-language steps so the result is explicit.
Does it run on every pull request and on a schedule?
Yes. Use pull request testing or a CI job against the preview deployment before merging. Enable Production Monitoring for the saved group to run recurring checks against the live store. Both appear in Results with their environment and trigger.
How do we get notified when a checkout fails?
Connect Slack or Discord, or enable email notifications for the project. Scheduled and webhook-triggered group runs can report failures with the test name, the step that broke and a link to the run's recording, screenshots and results.
