Release Confidence for a High-Volume Ticketing Platform
A testing strategy built from zero for a high-volume ticketing platform in Spain — backend integration and Playwright E2E, with a post-deploy gate.
Key Results
20 → 91
E2E coverage
End-to-end tests covering the critical purchase and check-in flows.
616
Integration cases
Backend integration test cases across core services.
3 gateways
Payments tested
Three payment gateways tested end to end, including 3DS, across 3 browsers.
Context
A high-volume ticketing platform in Spain needed to ship faster without breaking the flows their revenue depends on — ticket purchase, coupons, check-in, and ticket resending.
The problem
- No automated tests at all.
- Releases were validated by hand, which was slow and error-prone.
- The most critical flows — purchase, coupons, check-in, ticket resending — had no automation protecting them.
What we did
- Built a testing strategy from zero: backend integration tests plus end-to-end tests with Playwright.
- Added a post-deploy quality gate that runs the critical tests after every deployment.
- Tested three payment gateways end to end, including 3DS authentication, across three browsers.
- Embedded analytics with per-seller filtering so the business could see its own numbers.
Result
Release validation went from days to minutes, and the team could ship changes to critical flows without holding their breath.
Stack
Playwright · Backend integration testing · 3DS payment gateways · Embedded analytics