Context
As QA Lead on a hospitality loyalty app (loyalty, rewards redemption, bookings and in-app engagement, backed by a BFF layer and several third-party integrations), I owned test strategy, regression planning, stakeholder reporting and release sign-off. The full regression suite had about 1,000 manual cases, while the client’s release calendar gave QA about two days per release, and the team was shrinking from four people to two.
The first full regression I led took 7 active days with 4 QAs. More people or longer windows weren’t an option, so the gap had to be closed by changing what we tested and how. Development carried on during release weeks, test data depended on the client, and a third-party integration changed mid-run.
What I did
I ran the first regression as a measurement exercise as much as a quality gate: daily tracking reports built from test-management exports, every blocked case tagged by cause, and in-run scope decisions. Of the 979 executable cases, 962 passed (98.3%), with 17 defects logged and the release approved with 2 minor known issues.
The data showed 10 of 19 sections produced zero defects, while four sections produced 12 of the 17 failures. From that I wrote a four-tier release strategy (build acceptance, change-impacted, core business-critical, and rotating regression) with a capacity model of about 36 cases per QA per day and two agreed staffing profiles. When the next major version triggered a full regression, broader UI automation and earlier handling of test data let 2 QAs finish 1,002 cases in 4 days: 968 passed, 1 defect, and 33 blocked, each with a stated cause.
Tools used:
- TestRail
- Jira
- Maestro
- Charles Proxy
- Firebase/GA4
- Slack/Teams