Storefront · Search
Search Results That Ignored the Search
On the home page search, "Show All Results" listed every product instead of the ones that matched.
Case Study · E-Commerce
Edible Arrangements: WooCommerce Test Automation with Playwright and JMeter
Playwright automation for the storefront and admin panel, JMeter load tests for the APIs and Terraform tests for the Azure infrastructure.
engagement / edibleCompleted
- Client
- Edible Arrangements, US gifting e-commerce
- Platform
- WooCommerce
- Scope
- Storefront, admin panel, APIs, Azure infrastructure
- Environments
- Development and staging, plus any branch on demand
- Engagement
- About 1 year
- Team
- SprintSynergy QA automation team, led by our founder
- Stack
- PlaywrightTypeScriptJMeterTerraform (HCL)Microsoft AzureAzure DevOpsAllure
500+Automated Test Cases
90%of Manual Test Cases Automated
3Layers Tested: UI, API and Infrastructure
10KVirtual Users at Peak API Load
The Result
What Edible Ended Up With
- Releases with no blocker or critical bugs. Smoke and regression suites checked development and staging from Azure DevOps before changes went live.
- 90% of the manual test cases automated. 500+ Playwright tests cover the storefront and the admin panel.
- Three layers checked, not one. The UI in Playwright, the APIs under 5,000 to 10,000 virtual users in JMeter and the Azure infrastructure in HCL.
- A report for every run. Each pipeline run ends in an Allure report the team can read.
Overview
A Framework Built From Scratch
Edible Arrangements is a US gifting brand known for its fresh fruit arrangements. For about a year, SprintSynergy handled test automation for its WooCommerce e-commerce platform. We built a Playwright framework in TypeScript from scratch and automated 500+ test cases across the storefront and the admin panel: 90% of the application's manual test cases. We load tested the APIs in JMeter with 5,000 to 10,000 virtual users. For the Terraform infrastructure on Microsoft Azure, we wrote tests in HCL. Smoke and regression suites ran from Azure DevOps pipelines, with an Allure report for every run.
Test Setup · Three Layers
UI
StorefrontPlaywright · TypeScript
Admin PanelPlaywright · TypeScript
Azure DevOps PipelineSmoke · RegressionDev · Staging · Branch
Allure Report
APIs
JMeter, Run from the Cloud5K to 10K Virtual Users
Infrastructure
Terraform Tests in HCLNames and Credentials · Dev and Staging
The Problem
More Than the Pages Shoppers See
An online store can break in more places than the pages shoppers see. A release can stop sign-up or checkout from working. It can break an admin screen, slow an API down under load or leave a cloud service badly deployed.
The work covered all four, in both the development and staging environments, on a framework built from scratch.
What We Tested
Storefront to Infrastructure
- Storefront: registration, login, advanced search filters, add to cart and checkout, automated in Playwright with TypeScript.
- Admin Panel: automated tests for the WooCommerce admin panel the team uses to run the store.
- APIs Under Load: performance tests in JMeter, run from the cloud, with 5,000 to 10,000 virtual users.
- Infrastructure: tests written in HCL that check the Terraform-deployed services on Microsoft Azure, in development and staging. Each service has to be deployed properly, with valid names and credentials.
How We Built It
Playwright, Azure DevOps and Allure
- A Playwright Framework from ScratchWe built the framework in TypeScript on the page object model. Each page of the store and the admin panel is a page object. When a screen changes, we fix one page object instead of every test.
- Smoke and Regression SuitesA short smoke suite gives a quick health check, and the regression suite runs the wider set.
- Azure DevOps PipelinesThe pipelines run the smoke and regression suites against development and staging, and against a specific branch when the team needs it.
- Environment VariablesThe same tests run in either environment. Environment variables decide where each run points.
- Allure ReportingEvery pipeline run produces an Allure report that shows which tests passed and which failed.
- Infrastructure Tests in HCLOur tests confirm that each Azure service Terraform deploys is in place, correctly named and set up with valid credentials.
- Load Tests from the CloudJMeter test plans put the APIs under 5,000 to 10,000 virtual users.
What We Found
Three Bugs We Found
Storefront · Cart
Cart Items Lost Where a Surcharge Applied
In delivery areas with a surcharge, adding a product to the cart did not add it, so the bill was wrong.
Storefront · Cart
Delivery Offered on Days with None
The cart showed delivery as available on dates when no delivery ran.
What We Delivered
Handed Over
- 500+ automated test cases across the storefront and the admin panel, in Playwright with TypeScript, covering 90% of the application's manual test cases.
- Smoke and regression suites running from Azure DevOps against development, staging or a chosen branch.
- An Allure report for every pipeline run.
- HCL tests for the Terraform infrastructure on Microsoft Azure.
- JMeter load tests for the APIs at 5,000 to 10,000 virtual users.
Questions
Frequently Asked Questions
For Edible Arrangements we built a Playwright framework in TypeScript on the page object model. We automated registration, login, advanced search filters, add to cart and checkout, plus the admin panel. Smoke and regression suites ran from Azure DevOps pipelines.
More Case Studies
All Case StudiesRunning a WooCommerce Store?
Book a free 30-minute QA strategy call. A written QA plan follows within 48 hours.
Book a Free QA Strategy Call