Test an e-commerce site by following complete customer journeys—from product discovery through checkout and post-purchase tasks—then repeat those journeys with functional, accessibility, security, and performance checks. A page loading correctly is not enough: verify the interactive states and business rules that determine whether customers can actually complete an order.
Scope the store around customer journeys
Start with the jobs customers need to complete, then map the pages and states that support them. Include the store’s relevant templates and flows:
- Category browsing, search, sorting, and filters.
- Product details, options or variants, stock status, and quantity controls.
- Basket edits, shipping choices, taxes, discounts, and totals.
- Guest and signed-in checkout, including payment-provider handoffs.
- Order confirmation, order history, and returns or refunds where available.
For each important journey, record the normal route and meaningful branches. Examples include changing a delivery address, selecting a different shipping method, applying a promotion, signing in midway, or recovering from a declined payment. Record the action sequence and relevant state: a URL alone may not reproduce an interactive cart or checkout.
The W3C’s WCAG-EM 2.0 methodology offers a useful structure for defining scope, exploring the site, selecting representative samples, evaluating them, and reporting results. Its web-shop guidance treats selecting and purchasing an item as essential functionality and calls for testing the default purchase sequence and critical branches.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →#1 Best Overall
- The FreeStyle log book includes sections for: Lunch, Dinner, Bedtime, Night
- Comments for each day of the week
- Log Book Dimensions L=4.25" x W=3.12" x H=0.12"
- Contains 5 book
Build functional and regression checks
Turn the mapped journeys into repeatable checks. For each one, write the starting conditions, actions, expected outcome, and evidence to capture. Include normal behavior and recoverable failures:
- Discovery: Search results, filters, sorting, empty results, and links to products.
- Product selection: Variant changes, unavailable options, stock messages, and quantity limits.
- Basket: Adding, removing, and editing items; recalculated totals; and persistence after refresh or navigation.
- Pricing and delivery: Discount eligibility, tax and shipping display, address validation, and changes to delivery options.
- Payment: Success, decline, cancellation, retry, and return from a provider handoff.
- Order state: Confirmation, order history, and any supported cancellation, return, or refund steps.
- Interrupted flows: Browser back, duplicate submission, session expiry, refresh, and recovery after an incomplete checkout.
Make the test matrix fit the store’s actual rules. Product models, shipping regions, tax settings, promotions, inventory systems, account requirements, and payment gateways change which combinations matter; there is no universal matrix that covers every shop. Retest the affected journeys after material changes to themes, scripts, product forms, payment integrations, or checkout behavior.
Test accessibility in the shopping flow
Choose an applicable target standard and conformance level based on the business’s requirements and jurisdiction. Do not infer a retailer’s legal obligations from a generic checklist. WCAG 2 success criteria are testable, but evaluation is not an automated-only exercise: W3C says, “Testing the success criteria would involve a combination of automated testing and human evaluation.” See W3C’s Understanding Conformance guidance.
Rank #2
- Used Book in Good Condition
Check essential transaction steps—product selection, basket, login, and checkout—with a mix of methods. Look for:
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match- Keyboard access and a visible focus indicator for controls.
- Meaningful names, instructions, labels, and identification of form errors.
- Clear error recovery, including how to correct invalid or missing information.
- Readable contrast and usable zoom or reflow.
- Status messages announced when totals, stock, or validation results change.
- Dialogs that manage focus and can be operated and dismissed appropriately.
- Compatibility with the assistive technologies and browsers relevant to the audience.
Use automated scans to find some issues efficiently, then manually inspect behavior and test with assistive technologies. Where possible, include usability testing with people with disabilities. W3C notes that technical conformance alone does not guarantee usability for people with a wide variety of disabilities; its guidance also recommends usability testing. Google’s accessibility evaluation guidance recommends combining design, automated, manual, and assistive-technology evaluation and repeating audits throughout the product lifecycle. A passing scan is not a conformance claim.
Exercise payment and pricing logic safely
Test more than the appearance of a checkout form. In an authorized test environment, verify that the server enforces quantities, prices, promotions, basket contents, shipping, and payment outcomes. Follow the relevant scenarios in OWASP’s Web Security Testing Guide and use the payment provider’s sandbox or test methods rather than placing uncontrolled production orders.
Rank #3
- Try invalid or negative quantities only in a controlled environment and confirm server-side validation.
- Check promotion limits, expiration, and reuse rules.
- Change basket or delivery details and verify that shipping, discounts, and totals are recalculated rather than relying on stale values.
- Confirm the application verifies the actual payment result; visiting a success URL alone must not establish that an order was paid.
- Where supported, check duplicate submissions or callbacks and attempts to perform steps out of sequence.
Payment integration changes both the technical surface and compliance responsibilities. Redirects, embedded iframes, cross-domain forms, and backend handling of card data are not interchangeable. A generic checklist cannot establish PCI DSS scope or compliance. Confirm current obligations with the payment provider and appropriate compliance professionals for the actual integration, and only test systems for which you have authorization.
Measure performance with field and lab evidence
Use Google Search Console’s Core Web Vitals report to review field performance signals and follow its links for deeper investigation. PageSpeed Insights can provide field data and live test results for mobile and desktop; Lighthouse provides an in-browser test.
Free tools Windows power users keep installed
One-click scans. No signup required.
Keep observed field data distinct from a one-off lab run. A live test describes a particular test at a point in time; it is not equivalent to performance experienced by users over time. In reports, identify the device class and whether each result is field or lab evidence. Verify current metric names and thresholds in Google’s documentation before publishing or applying thresholds; do not treat an isolated score as a complete account of storefront performance.
Capture visual evidence without mistaking it for a full test
Screenshots can help document a particular page state, compare changes, and attach visual evidence to a repeatable test. They do not establish that a checkout works, that content is accessible, or that server-side pricing rules are secure. Capture the relevant state—such as a validation error, selected product option, or order confirmation—and keep the steps needed to reproduce it with the evidence.
For programmatic captures, ScreenshotNeo is a website screenshot API and MCP server. Its cleanup can accept consent banners and remove more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each cleanup step can be disabled. It bills only clean shots: bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, with the outcome identified in response headers. Its MCP server provides screenshot and PDF capture tools for AI agents. Screenshot capture remains evidence for visual state, not a substitute for the functional, accessibility, security, or performance evaluations above.
Or skip the browser setup
Make a screenshot request with one GET call. See the ScreenshotNeo API documentation for parameters and response details.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpCookie banners, popups, and chat widgets are removed before the shot; bot checks, blank pages, and failed loads are never billed. AI agents can take screenshots through its MCP server. The free plan includes 1,000 screenshots per month with no card, and paid plans start at $5 for 3,000. Sign up for 1,000 free screenshots a month, no card required.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Report findings so they can be fixed and retested
Give each finding enough context for another person to reproduce and verify it. Record:
- The page template or journey and the starting state.
- Steps to reproduce, expected behavior, and actual behavior.
- User or business impact, with a clear reason for the assigned severity.
- Evidence, an owner, and the retest outcome.
For accessibility issues, note the relevant criterion and the browser and assistive-technology context when applicable. For performance, state device class and whether the evidence is field or lab data. For security checks, record the authorized environment and scope, and avoid exposing customer or payment data.
Keep the test plan current
Store the journey steps, test data, expected outcomes, and evidence alongside the team’s delivery process. Review them whenever a change affects a customer path or its rules. Prioritize retesting the flows that changed, plus any critical downstream steps they can affect—for example, a product-form change can alter basket contents and checkout totals. Use automation for repeatable regression checks, and retain human evaluation for accessibility, usability, and other judgments that a tool cannot establish.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsFrequently Asked Questions
Can automated accessibility testing find every WCAG issue?
No. Automated tools can identify some issues, but W3C calls for a combination of automated testing and human evaluation. Manual inspection, assistive-technology checks, and usability testing with people with disabilities add evidence automation cannot provide.
Should I test checkout on the live store?
Use the payment gateway’s sandbox or test methods for payment scenarios and avoid uncontrolled production orders. Security testing must also be authorized and limited to the intended environment.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
