
Puma
Global e-commerce relaunch — web & first-ever mobile app
First mobile app. Full rebrand. Global launch.
We led testing and test automation for Puma’s biggest digital programme to date — a global e-commerce relaunch, the company’s first-ever mobile app, and a full website rebrand on a modernised tech stack — across Europe, the UK, North America, South Asia and the Middle East. We built the QA programme from scratch and supported the marketing team with Sanity Studio component development, alongside validating payment flows across multiple processors and regions.
Puma's biggest digital programme to date.
A global e-commerce relaunch, a full website rebrand, a modernised tech stack — and the company’s first-ever mobile app. Built on Salesforce Commerce Cloud, paired with Sanity Studio CMS, multiple payment processors and an internal back-office system. The programme spanned 27 months, with delivery across Europe, the UK, North America, South Asia (including India), the Middle East and additional Asian markets. We led the testing and test automation for the entire programme — web, mobile, and everywhere they connect.
Scalable, reusable — 100,000+ test cases run every week.
We built the testing strategy and test automation capabilities from scratch — and we built them to scale. The suite grew into thousands of well-architected, highly reusable end-to-end Cypress test cases. Reuse is what made the volume sustainable: instead of bloating the codebase, we ran the same well-engineered suite many times, in many contexts.
By steady state, the suite was running roughly 15–20 times every day across the delivery pipeline — on every pull-request build, on every automatic environment deployment, on every release branch. By the end of a typical week the platform had been exercised by 100,000+ test cases — not because we wrote 100,000 tests, but because the same well-engineered tests ran consistently across the whole development lifecycle.
The framework was designed for independent, parallel execution from the ground up. No shared state, no order dependencies, no mystery flakiness from one test polluting another. That meant the full suite finished in roughly 8–12 minutes regardless of how it grew, instead of the hours it would have taken running sequentially. Fast feedback wasn’t a bonus — it was the architecture.
Supporting the CMS the marketing team uses every day.
An important part of the engagement was working alongside Puma’s marketing team on their Sanity Studio CMS — not leading it, but supporting it. We contributed to the development of content blocks, schemas, custom inputs and preview surfaces with the marketers, then tested it all end-to-end so they could launch campaigns on multiple environments without engineering hand-holding.
- Sanity Studio component development in support of the marketing team
- Custom schemas, content blocks and structured inputs built collaboratively
- Preview & production parity validated end-to-end
- Test data and fixtures built so non-engineers could trial a campaign before it went live
- Direct collaboration with brand and growth on launch readiness
Stock, inventory, sales, customer profiles.
Validated the Salesforce Commerce Cloud (SFCC)integration end-to-end — product catalogue, stock, inventory, sales, customer profiles. A small Playwright framework covered the back-office system separately so the ops team had its own quality bar.
Every journey. Every integration. Every region.
Payment was where regulators, partners, regions and processors all collided. We tested it in flight, end to end — every customer journey on the front, every integration on the back, every locale-specific edge case in between.
Payment journeys. Full checkout flows per method: cart through 3D Secure / SCA step-up auth through confirmation to order management. Guest checkout, returning customers, saved cards, express wallet checkouts (Apple Pay / Google Pay / PayPal), failed-payment retries, partial refunds, full returns. Each region had its own valid combinations — we covered them all.
Payment integrations. Validated the back-end payment layer too: tokenisation, processor webhooks, async payment-status sync, retry-on-timeout, multi-currency handling, regional tax calculations and order-state propagation. Adyen and Ocapiran in parallel as the two integrators — we had to keep both sides green.
- Visa, Mastercard, Amex — across 3 regions and currencies
- Apple Pay, Google Pay, PayPal express checkouts
- 3D Secure / SCA challenge flows, including step-up authentication
- Adyen & Ocapi integration validation in parallel
- Tokenisation, webhook delivery and async status sync
- Partial & full refunds, order amendments and cancellations
- Failed-payment retries, fallback methods and recovery journeys
- Multi-currency display, conversion and per-region tax handling
Puma's first-ever mobile app. We tested it like it was.
The first native mobile app in Puma’s history — built in React Native and shipped globally. Automated with Detox, run against real devices and real network conditions on every release, paired with manual exploratory testing for the bits automation will never catch. Responsive web tested in lockstep so the brand felt the same everywhere.
- React Native, automated with Detox
- Real-device testing across iOS & Android matrices
- Responsive web parity tested alongside the app
- Manual exploratory testing on every release
WCAG, Section 508 (USA), Lighthouse benchmarks.
Accessibility tested against both WCAG and Section 508 standards (US) — manual and automated, with cypress-axe integrated into the framework. Google Lighthouse benchmarks were embedded into the automation so UI performance had a quality gate, not just a hope.
Merge to main, into production — fully autonomous.
CI/CD pipelines in GitHub Actions made the automated test suite a first-class part of the delivery flow. Every pull request ran the relevant tests across multiple environments before merging.
The end-state was an autonomous pipeline from merge to main all the way through to production — with a ~45-minute turnaround for small fixes. No manual hand-off, no release theatre, no late-night deploy calls. The tests were trusted enough to gate real money.
What we delivered
- Test strategy from scratch
- Scalable, reusable test architecture
- Parallel test execution (8–12 min full suite)
- UI automation framework (Cypress BDD)
- API automation
- Component unit tests (Jest)
- Mobile automation (Detox)
- Back-office automation (Playwright)
- Sanity Studio component support & development
- Marketing team enablement
- Payment journey testing (cards, wallets, 3DS / SCA)
- Payment integration validation (Adyen, Ocapi, webhooks, tokenisation)
- Multi-region localisation & currency testing
- SFCC integration testing
- Accessibility (WCAG, Section 508)
- Performance (Lighthouse, embedded)
- CI/CD (GitHub Actions)
- UAT & exploratory testing
Tech & tools
- TypeScript
- JavaScript
- Next.js
- React
- GraphQL
- AXIOS
- Cypress
- Cucumber
- Jest
- Detox
- Playwright
- Salesforce Commerce Cloud
- Sanity
- Adyen
- Ocapi
- GitHub Actions
- Lighthouse
- cypress-axe
- JIRA
Selected coverage of Puma’s e-commerce platform on Salesforce Commerce Cloud.
- SalesforcePUMA takes a mobile-first approach to ecommerce
- CETDIGITPUMA leverages Salesforce to relaunch its mobile sites and scale customer expectations
- Salesforce LivePUMA drives ecommerce growth across 29 countries with a mobile-first strategy
External links open in a new tab. QA Tech is independent and not affiliated with Puma or Salesforce.
Got a multi-region launch coming up?
We’ve done it before. Across three continents, two devices and a dozen payment methods.
