Behind every smooth checkout is a lot of testing. This page is a working checklist of test cases for an online shopping website, grouped by area of the site, so you can pick the areas you own and turn each line into a test. For step by step examples with test data, see our 16 sample e-commerce test cases, and for the strategy behind them read the ecommerce testing guide.
Table of Contents
ToggleHow to use this checklist
Work from the money path outward. Start with search, cart, checkout and payment, since a defect there costs sales immediately. Then move to accounts, returns and promotions, and finish with performance, security and mobile. Mark each item by priority and decide which ones to automate. Good test coverage means every important area has at least a happy path test, a negative test and an edge case.
1. Registration, login and account
- Register with valid details; confirm the account and welcome email.
- Register with an existing email, a weak password, a bad email format and empty required fields; each shows a clear message.
- Log in with the right credentials; log in with a wrong password and confirm the error does not say which field was wrong.
- Lockout or throttling after repeated failed attempts, as your policy defines.
- Password reset: request, receive link, set new password, old link stops working.
- Edit profile, addresses and saved payment methods; changes persist.
- Log out clears the session; the back button does not reveal account pages.
2. Search, filters and sorting
- Keyword search returns relevant results, handles typos and shows a useful page for no results.
- Each filter (price, brand, rating, category) works alone and in combination.
- Sorting by price, popularity, rating and newest gives the right order.
- Filters can be removed and reset; the result count updates.
- Pagination or infinite scroll loads every item once, with no duplicates.
Wrong filters frustrate shoppers and cut conversion. A mix of automated UI checks and manual test cases catches most issues.
3. Product page
- Images load; zoom and carousel work.
- Selecting a colour or size updates the image, price and stock, and the cart receives the correct variant.
- Stock status is accurate; out of stock items cannot be bought.
- Reviews and ratings show correctly, and new reviews can be submitted and moderated.
- Delivery and returns information is visible and correct.
4. Cart and wishlist
- Add, remove and change quantity; subtotal and tax update correctly.
- Quantity limits and stock limits are enforced with a helpful message.
- Cart persists across page refresh, logout and login, and devices if the design says so.
- Price changes or stock changes while an item is in the cart are shown clearly.
- Add to and remove from wishlist; move items from wishlist to cart.
5. Checkout and payment
- Guest checkout and logged in checkout both complete.
- Address validation accepts valid addresses and rejects invalid ones with clear messages.
- Shipping options and costs match the destination and weight.
- Each payment method works: cards, wallets, bank transfer and cash on delivery where offered.
- Declined card, expired card, wrong CVV and insufficient funds: a clear message, no order created, no charge.
- Extra authentication such as 3D Secure succeeds and fails gracefully.
- Double clicking “Place Order” or refreshing creates one order and one charge.
- Confirmation page and email show the right items, totals and delivery details.
Example: Test case “Expired credit card entry”. Expected: the site shows a clear “invalid card” message and stops the transaction. Use your payment gateway’s sandbox test cards, never real cards.
6. Promotions and coupons
- A valid code applies the right discount; an invalid or expired code is refused with a message.
- Usage limits, minimum spend and product exclusions are enforced.
- Stacking rules work as designed when several offers apply.
- Discounts are removed correctly when items leave the cart.
7. Orders, returns and refunds
- Order history shows the right status at each stage.
- Cancel an order before shipping; stock is restored and payment is refunded.
- Start a return within the allowed period; the request is refused after it.
- Refund amounts and timing match the policy, and status emails are sent.
8. Mobile and compatibility
- Layout adapts across screen sizes and orientations.
- Buttons, menus and modals work by touch; forms use the right keyboard type.
- Key flows work on current browsers and operating systems your customers use.
Repeating these on many devices is slow by hand, so automate the stable flows. Our guide to test automation frameworks helps you choose an approach.
9. Performance
- Page load time on home, search, product and checkout pages meets your targets.
- Concurrent users can check out at peak load without errors or slow responses.
- The site recovers after a traffic spike or a failed dependency.
- Large catalogues and many images still load quickly.
Simulate load with JMeter, k6 or Gatling; compare them in our load testing tools guide, and read the wider performance testing guide for planning.
10. Security and privacy
- Passwords are stored hashed, never in plain text; sessions expire and tokens are protected.
- Inputs resist SQL injection and cross site scripting.
- Customers cannot see other customers’ orders by changing an ID in the address.
- Card data is handled by a compliant payment provider and never logged.
- Consent, data export and deletion requests work where privacy law applies.
11. Backend and data checks
UI tests are not enough. Many serious defects sit behind the screen, so add checks for:
- Order creation, queueing and status updates in the database.
- Stock deduction and restoration, including when two buyers want the last item.
- Tax, shipping and discount calculations at the API level.
- Invoice and email generation, and integration with inventory, shipping and payment systems.
How to write a good test case
A good test case has a clear title, preconditions, numbered steps, specific expected results and a link to the requirement it covers. Keep each case short and focused on one behaviour. You can keep cases in a spreadsheet, in a test management tool such as TestRail or Zephyr, or as code (Cypress, Playwright) when you automate. Teams exploring AI help with test design should read AI in software testing, and the principles behind prevention versus detection are in what is quality assurance.
Frequently asked questions
What are the main test cases for an online shopping website?
Registration and login, search and filters, product page, cart, checkout and payment, promotions, returns, mobile behaviour, performance and security.
How do you test the cart?
Add, remove and change items; check subtotal, tax, discounts and stock limits; confirm the cart survives refresh and login; and check what happens when price or stock changes.
What are the key payment test cases?
Valid payments for each method, declined and expired cards, wrong security codes, extra authentication, duplicate submissions and the confirmation after payment.
Why are negative test cases important?
They show how the site handles bad input and failures, such as an expired coupon or invalid card. A shop that fails gracefully keeps customer trust.
How can I automate these tests?
Use Selenium, Cypress or Playwright. Write modular scripts for the stable flows (login, search, cart, checkout) and run them in your pipeline for regression.
How do I cover mobile?
Test several screen sizes, orientations and touch actions on real devices or a device cloud such as BrowserStack.
Conclusion
Good test cases for an online shopping website start with the path that earns money and extend outward to everything that protects it. Use this checklist to find gaps, the sample test cases to write them down, and the ecommerce testing guide to plan the whole effort.
Part of our guide to Ecommerce Testing. Start with the complete Ecommerce Testing guide, or read the related articles:
Want more testing guides in your Google results? Add Testmetry as a preferred source.




