Test the shopping journey that produces an order—not just whether the storefront loads. Combine quick code checks, a small set of automated browser journeys, performance testing, and human review. Run the relevant checks as code changes and before release, then use real-world performance data to see whether the change worked for shoppers.
What ecommerce website testing should cover
A useful test plan follows what a shopper does and what the store must do in response. A product page can render correctly while a variant selector, cart, shipping rule, payment configuration, or order notification is broken.
As an Amazon Associate I earn from qualifying purchases.
Shopify’s guidance is one concrete platform-specific example: a test order can check checkout settings and order processing, inventory, shipping, email notifications, and taxes. Shopify supports test orders through a test gateway or Shopify Payments test mode. These checks and settings are Shopify-specific; use the equivalent test-payment process documented by your own commerce platform.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Map the order journey
- Find a product using the storefront’s search, navigation, or collection pages.
- Choose a variant or configuration, and verify that price and availability match the selection.
- Add the item to the cart, change quantity, remove it, and confirm totals update as expected.
- Apply a relevant discount and check both accepted and rejected code behavior.
- Enter shipping details and verify that the expected shipping options and costs appear.
- Complete checkout through an approved test-payment route, then verify the resulting order and downstream handling.
Add cases specific to your store: unavailable inventory, invalid or incomplete inputs, and the checkout options you support. Test both a successful order and expected blocks or error messages. For example, Shopify checks inventory as a customer progresses through checkout and displays an error if inventory is no longer available. Its server-side Cart and Checkout Validation Function API can enforce cart and checkout rules, including in express checkout flows, and return targeted validation messages. Those are Shopify behaviors, not platform-neutral implementation instructions.
#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
Cover the storefront around checkout
Test the interactions shoppers rely on: navigation, product forms, menus, search, filters, cart controls, and any dialogs or overlays. Include accessibility and browser compatibility review, not only visual checks in one browser. Shopify’s theme-testing guidance also suggests checking whether navigation and product forms still work with JavaScript disabled, and considering review by people outside the development organization.
Choose test layers by risk and speed
Use multiple layers rather than expecting one kind of test to catch everything. The right balance depends on the store’s architecture, release risk, and team; there is no universal suite ratio established by the sources cited here.
| Approach | Best suited to | Trade-off |
|---|---|---|
| Code or theme checks | Fast feedback on implementation issues. Shopify theme developers can use Theme Check to analyze Liquid code. | They do not prove that a shopper can complete an order. |
| Integration checks | Verifying exchanges among store services, data, and integrations. | They cover service behavior but may not catch a broken user-visible journey. |
| Automated browser journeys | Checking visible shopping steps, including success paths and expected inventory or validation errors. | Keep the critical flows focused so failures are easier to diagnose and tests stay maintainable. |
| Lab performance audits | Reproducing performance issues and detecting regressions under controlled conditions. | A lab run is not a complete picture of visitors using different devices and networks. |
| Field performance monitoring | Understanding performance experienced by actual visitors, including differences by page, device, or region where the platform provides that breakdown. | It describes deployed experience; it does not replace repeatable pre-release checks. |
| Human exploratory and accessibility review | Finding confusing, inaccessible, or unexpected behavior that a scripted assertion may not judge well. | It requires human time and complements, rather than replaces, repeatable automation. |
Run repeatable checks in the development and release workflow
Run fast checks as developers make changes, and run the relevant automated journeys on changes or pull requests. Before release, run broader coverage that includes a test order and the integrations affected by the change. Retain scheduled checks where they help catch issues caused by changing catalog data, third-party services, or configuration.
For Shopify theme work, Theme Check can analyze Liquid code. Shopify also documents Lighthouse CI as an option for performance audits on pull requests. Its theme guidance recommends keeping device and network conditions consistent and taking multiple Lighthouse runs. Apply those specific tools to Shopify themes; other platforms may have different official checks.
Rank #2
- Used Book in Good Condition
Make failures actionable
- Give each test a clear purpose and assert the expected result, not just that a page appeared.
- For checkout tests, record which stage failed and whether the expected validation message appeared.
- Keep test data and the payment mode clearly identified so a test cannot be mistaken for a live transaction.
- When a test fails, distinguish an application defect from a test-environment, data, or third-party-service problem before changing the test.
Measure performance with both lab and field data
Use field measurements to identify pages and visitor conditions that need attention. Use lab tests to investigate and watch for regressions, then check field data again after deployment. Shopify notes that lab results can differ from real-user monitoring because a lab run uses one device and simulated network conditions.
Shopify currently identifies Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS) as Core Web Vitals. Its documented “good” thresholds are LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1; its overall “good” assessment requires at least 75% of page loads to meet the good thresholds. These are Shopify’s published criteria, not a promise that meeting them guarantees conversion, accessibility, security, or compatibility.
Performance can be affected by apps, third-party and analytics libraries, theme code, and image or video size. Shopify also advises measuring the effects of checkout UI extensions using a throttled mobile profile and comparing the same checkout step. That comparison is meaningful only when the test conditions are held consistent.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Keep Shopify Theme Store rules in their lane
For Shopify Theme Store submissions, Shopify documents a benchmark using repeated Lighthouse runs on the home, product, and collection pages under consistent conditions, with median scores used. Its stated acceptance threshold is a minimum average Lighthouse performance score of 60 across those three page types on desktop and mobile. This is a Shopify Theme Store submission rule, not a general ecommerce performance target.
Rank #3
What automation catches—and what still needs people
Automation is strongest when the expected behavior is known and repeatable: a variant changes the displayed price, a valid discount changes the total, unavailable inventory blocks checkout, or a test order triggers the expected handling. It can catch regressions before shoppers encounter them and make critical checks repeatable across releases.
Automation does not determine by itself whether a shopping flow is understandable, whether a page is usable with assistive technology, or whether a change improved business outcomes. Pair it with exploratory review and accessibility evaluation. Shopify advises considering reviewers outside the development organization for theme testing. After deployment, monitor actual outcomes and field performance rather than treating a passing test run as proof of impact.
Screenshot a page for visual checks
A screenshot can help review a page’s appearance at a specific viewport, but an image alone does not verify that cart actions, checkout rules, accessibility, or order processing work. Treat visual comparison as one part of the test plan, and make sure the capture represents the state you intend to review.
Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server for developers. A single request can return a PNG, JPEG, WebP, or PDF. Its capture flow can accept cookie or consent banners and remove more than 60 known consent platforms, newsletter popups, and chat widgets before the screenshot; each step can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and responses identify the page verdict and billing status in headers. Its MCP server provides take_screenshot, get_page_info, and capture_pdf for AI agents and MCP clients. See the ScreenshotNeo website and API documentation.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpThe Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots. Sign up for free and try 1,000 screenshots a month with no card.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshoot common testing failures
A test order is charged or cannot be placed
Check that the payment provider is in its documented test mode and that the test order is using the intended test route. Shopify warns that customers cannot place live orders while providers are in test mode, so confirm the mode before testing and restore the intended live configuration afterward. For another platform, follow its own payment-provider instructions.
Checkout fails after inventory changes
Check the available inventory and whether the test expects the item to remain purchasable. In Shopify, checkout checks inventory as the customer completes steps; an item that is no longer available produces an error. Assert the expected blocked-order behavior as well as the successful path.
Free tools Windows power users keep installed
One-click scans. No signup required.
A browser journey passes but orders are mishandled
A page-level success assertion may stop before downstream processing. Verify the test order’s handling, inventory effects, shipping, notifications, and taxes as appropriate to the platform and configuration; Shopify’s test-order guidance explicitly includes these areas.
A performance score changes between runs
Check whether the device profile, network conditions, page state, or run count changed. For comparable Shopify theme measurements, use consistent conditions and multiple runs; Shopify’s documented Theme Store benchmark uses the median. Use field data as a separate view of visitors’ actual conditions.
A Lighthouse result conflicts with visitor experience
Do not assume either measurement is wrong: lab and field data answer different questions. Shopify notes that Lighthouse lab conditions use a single device and simulated network, while real-user monitoring reflects actual visitors. Use the field signal to choose what to investigate, then reproduce likely causes in a controlled lab run.
Frequently asked questions
Does passing automated tests prove the store is ready?
No. It shows that the tested expectations passed under the test conditions. It does not establish that every shopper can use the experience or that the change improved business outcomes.
Recommended Free Tools
Is a Lighthouse score a conversion guarantee?
No. A performance score is not proof of conversion, accessibility, security, or browser compatibility; test those concerns separately.
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.
