I currently have 5 clients and they want to ship something daily. During these deploys I usually forget to test some edge cases — products that have no relation to the change but somehow something is wrong with them at 3am.
So right now after each change I am manually testing the whole website for 30 minutes. I believe devs out there are doing this in a better way so please let me know how you guys are monitoring client sites.
Hi @jai_mishra
The process for testing really depends on the types of changes you’re making but the first thing to use would be theme check - a linter for Liquid and JSON. It catches syntax errors, missing templates, unused variables, deprecated tags, and performance issues. You can run it via Shopify CLI:
shopify theme check
It also integrates with the Shopify Liquid VS Code extension so you catch issues as you code.
You could also try end-to-end testing with Playwright or Cypress - you can use these to write automated tests that navigate your client’s storefront and verify critical flows:
- Homepage loads, key sections render
- Collection pages show products with images and prices
- Product pages have an add-to-cart button that works
- Cart updates correctly
- Checkout initiates (you can test up to the checkout redirect)
Playwright is a good fit here - it’s fast, supports multiple browsers, and handles Shopify’s dynamic content well.
Agreed, Playwright can automate virtually all of these checks on Shopify Plus — including production stores protected by Cloudflare bot detection.
Here are two live examples:
Oh Polly framework — demo video
Hunter Boots framework — demo video
Both cover collection pages, add-to-cart, bag continuity and checkout entry across desktop and mobile.
Theme Check catches code issues before deploy. Playwright able to catch broken user journeys after deploy — on the real site, across desktop and mobile.