a1qa and an anonymised fashion and apparel retailer: Ecommerce platform functional testing case analysed (case 1)

Verdict: what is checkable

Client profile as published

Client

a high-street fashion brand headquartered in London (the vendor's description; the vendor does not name the client)

Segment

Fashion and apparel

Region

United Kingdom

Channels

stores, ecommerce and mobile

Size indicators

300+ brick-and-mortar stores across the UK, Ireland, and internationally; 6 dedicated online stores

The client description and size indicators are quoted from the source; segment, region and channels are this site's classification. [ev-1079]

Systems in scope

• Ecommerce platform: named in the Challenges section ("transferring their eCommerce platform from monolithic to microservices-based architecture"); platform not named
• Mobile commerce: named in the Solution section ("native mobile apps (Android, iOS) in the regression testing scope")
• Payments: named in the Solution section ("The modules of payment and discounts")
• Integrations: named in the Solution section (microservices testing of how the services interact)

Where the source names each system is quoted or summarised from the case page. [ev-1079]

Problem as stated

The client kept adding features to its online stores while moving its ecommerce platform from a monolith to microservices. Some tasks were too large to finish within one sprint under its definition of done. To release new features faster, it looked for extra nearshore QA specialists with functional testing and test automation experience. [ev-1079]

some tasks were too large to complete them within a sprint (quoted from the source)

Approach

Testing types

functional, automation, mobile and api (main scope: functional)

Team shape

4 QA specialists engaged; They assisted 2 client delivery teams

Duration

2+ years of project duration

Engagement model

staff-augmentation

Tooling named in the source

Java, Cucumber, JavaScript, WebdriverIO, Atlassian Jira/Confluence, DbVisualizer, BrowserStack, Kobiton, Qubit

Metrics claimed

What the case does not say

• Baseline before the engagement.
• Measurement method.
• Duration over which the metric held.
• What was out of scope.
• Whether the client is still a client.
• Date of the work.

Reading notes for a buyer

This case speaks to the scenario “Ecommerce platform migration” and feeds dimension D2 (Retail system coverage) of the methodology. A question to put to a1qa:

By how much did QA costs fall, against what baseline, and over which part of the move to microservices? [ev-1079]

Source and verification

Source

a1qa delivers QA support for a global fashion brand’s website

Published

not dated by the vendor

Verified

2026-10-30

Evidence grade

secondary

Corroborating sources

none found

Vendor profile: a1qa. System facet: Ecommerce platform testing vendors.