Context
Early in my career, I joined a cross-functional team responsible for expanding the digital presence of a major restaurant group. The scope was significant: improve partially built native mobile apps, build a new website from scratch, including a CMS (Sitecore) and an integrated ordering experience, and eventually absorb additional brands under the same umbrella, including their loyalty platform.
The project demanded a QA strategy that could scale across multiple brands, multiple platforms, and a growing team.
What was built
The automation coverage spanned five dimensions, all running automatically on every push to the QA environment:
Functional testing via a Cypress-based web suite with Page Object architecture built for scale and multi-brand reuse. Visual regression via Percy to catch layout and component breakage on a CMS-heavy frontend. Accessibility checks via Axe-core covering WCAG compliance across page templates. Performance load testing via k6 targeting key user flows in staging. Security scanning via OWASP ZAP integrated directly into the CI/CD pipeline.
Tools used:
- Cypress
- Percy
- Axe-core
- k6
- OWASP ZAP
- Maestro
- Robot Framework