Ecommerce QA testing: what to test by hand and what to automate
A practical guide to ecommerce testing. The checkout, cart, search and payment checks every online store needs, which ones to test manually, and which to automate.

An online store can look perfect and still lose sales every day. The product page loads, the photos are sharp, and somewhere between the cart and the confirmation page some customers hit something that makes them give up. They do not email you about it. They buy from someone else.
Ecommerce QA testing is the work of finding those places. This guide covers what to test, and how to split the work between a person and a script.
Why stores break in ways other sites do not
A brochure website has pages. A store has state: what is in the cart, which discount applies, how much stock is left, which currency the customer sees, whether they are signed in. Every one of those can be right on its own and wrong in combination.
Most serious ecommerce bugs are combinations:
- A discount code that works, and free shipping that works, but not both together.
- A product that is in stock when added to the cart and sold out by the time of payment.
- A price shown in one currency and charged in another.
- A guest order that cannot be found later because no account exists.
What to test by hand
Manual testing is the right tool wherever judgement is needed, or where the path changes each time.
The full purchase, as a first-time customer
Start from a search engine or an ad, not from your home page. Find a product, choose a size, add it, change your mind, remove it, add another, and buy it. Do this on a phone with one hand.
Watch for anything that makes you hesitate: a delivery cost that appears late, a form that asks for the same thing twice, a button hidden under the keyboard.
Search, filters and sorting
- Search for a product with a spelling mistake.
- Search for something you do not sell. Is the empty page helpful?
- Apply three filters at once, then remove one.
- Sort by price and check the first and last items.
Product pages
- Every size and colour option, including the ones that are sold out.
- Photos on a small phone and a wide monitor.
- Price, discount price and "you save" figures that agree with each other.
Emails and what happens after the order
Order confirmation, dispatch notice, password reset and refund email. Read each on a phone and press every link. This area is often not tested at all, and it is what the customer sees last.
What to automate
Automation suits checks that never change and must never fail. In a store that is a short list, and it is the most valuable one.
- Add to cart and check out with a test card, start to finish.
- Cart totals: item price, quantity, discount, tax and shipping adding up correctly.
- Sign-up, sign-in and password reset.
- Discount codes: valid, expired, and used twice.
- Stock limits: you cannot buy more than exists.
- Each payment method you offer, in the provider's test mode.
Run these on every release and once a day against the live store. A daily automated purchase is the cheapest alarm you can have: if checkout breaks at midnight, you know before the morning's orders are lost.
We write these with Playwright, which runs the same checks in Chrome, Safari and Firefox.
Payment checks people forget
- A declined card must not create an order.
- Pressing Back during payment must not charge twice.
- A closed tab mid-payment should leave the order in a clear state, not half-paid.
- The amount on the bank statement must match the amount on the page, to the cent.
- Refunds must reach the customer and update the order.
Before a sale or a busy season
Extra traffic finds weaknesses that a quiet week hides. Two weeks before a large sale:
- Run the full manual purchase again on phones.
- Test the sale prices and codes on a copy of the store before they go live.
- Check what the store does when a product sells out while people have it in their carts.
- Consider performance testing if you expect several times your normal traffic.
Manual and automated, together
The two are not alternatives. Automation guards the paths that must always work. A person explores everything else, and notices what a script cannot: that a page is confusing, that a message is rude, that the cheapest shipping option is hidden. Our post on manual vs automated testing explains the split in more detail.
If you run a store and want the checkout tested by someone who has never seen it, start a project. We test websites and mobile apps, and can set up the daily automated purchase check for you.