// projects / eventbookings
Eventbookings - Event ticketing platform
Multi-tenant event-ticketing SaaS. Full QA ownership - requirements, manual, API, and a 2,000+ test Playwright web + API suite covering the full booking-to-payment flow.
EventBookings is a multi-tenant event-ticketing platform handling real money at scale - events, ticket types, seating, discounts, subscriptions and Stripe / PayPal / offline payments, where a single checkout bug is visible to thousands of buyers at once. Quality ran end to end across the project: requirements analysis and test-case design, manual and exploratory testing, API testing, and a 2,000+ test Playwright web + API framework - treated as a product in its own right, not a bolt-on, and now the gate every release has to pass.
Approach
Coverage is deepest on the path that earns - the booking-to-payment journey, from browsing an event and choosing tickets and seats through discounts, checkout, payment and confirmation, across single, timeslot and multi-session events, with refunds and RSVPs on top. The hard problems got first-class solutions: real transactional email is verified end to end (confirmations, OTPs, reminders, refunds), including negative checks that fail if an email which should be suppressed ever sends - something most suites can’t test at all - and every purchase is reconciled against the financial API, so revenue, fees and balance are proven at the source instead of read off a screen.
Making a suite that large fast enough to run before every release - not overnight - took two tiers of parallelism, session reuse and parallel-safe test data, with a custom live dashboard that surfaces failures mid-run and Allure/JUnit driving CI; the purchase flow is load-tested under concurrency on the same framework, and the whole thing scales with the hardware it’s given.
Impact
Pre-release checks for a new event type went from a multi-day manual cycle to a push-button gate - and with the payment and email paths genuinely proven, the team shipped a refund-handling refactor with no rollback window, a change it wouldn’t have risked before.