Use case: E-commerce
End-to-end testing for e-commerce
In a shop, search, cart, checkout, payments and account are the flows where a broken release costs orders the same day.
Flows to cover first in e-commerce: search, cart, checkout, payments, account. Each flow becomes a spec: a YAML file with plain-English steps that runs locally or in CI.
- Checkout is the flow most worth a test on every pull request; the step tells the platform what to click in plain English.
- Promotions and page layouts change weekly. Locator and layout changes are healed; a changed price or total fails the test.
- A failed checkout test gets a triage card with the failing step, the page state and the diff from the last passing run.
1name: Checkout with a saved card2url: https://app.example.com3tags: [checkout, smoke]4env:5 EMAIL: ${TEST_EMAIL}6 PASSWORD: ${TEST_PASSWORD}7steps:8 - Log in with EMAIL and PASSWORD9 - Open the cart10 - Click "Checkout"11 - Choose the saved card ending in 424212 - Click "Place order"13 - assert: The order confirmation page shows an order numberCapabilities used
Tests in plain English
A test is a list of steps in plain English in a YAML file; the platform resolves each step against the live page at run time.
Read moreHeals locator and layout changes
When a step no longer resolves because an element moved, was renamed or restyled, the platform re-resolves it, marks the test as healed and records the change for review.
Read moreTriages failures
A failed test gets a triage card with the failing step, the page state, the diff from the last passing run and a classification: app bug, test issue, environment.
Read moreParallel hosted runs
Runs tests in parallel on hosted browsers in the selected region with traces kept for the plan's retention window.
Read moreCommon integrations
Questions
Should checkout tests use real payments?
No. Point the test at a staging or preview environment with a test card from your payment provider.
Does the platform test page speed or load?
No. It runs functional end-to-end tests. API steps do not replace load testing.
Request early access
Early access: prices are the planned list prices. Billing starts when the platform enters beta; early-access use is not charged. We reply within 24 hours on business days.