- Context
- A superapp integration that consolidates 14 standalone applications into one platform, plus 3 new application projects, each built by a squad of 10–20 developers.
- Problem
- A user journey passes through applications owned by different teams. Each part can pass its own tests while the journey still fails.
- My role
- Lead a team of 30 QA engineers, coordinate shared regression checks across squads, and run one release review.
- Approach
- Map each shared journey end to end, include the handoffs between applications in the regression scope, and use contract testing and service virtualization so squads can test in parallel.
- Release review
- Four questions: scope, test evidence, open risks, and the decision with its reason. The template is below.
- Decisions and trade-offs
- Two calls shaped the work. First, judge a release on the whole journey, not per application — it costs more coordination across squads, but testing each application alone leaves the handoffs unchecked. Second, let squads test in parallel with contract testing and service virtualization instead of waiting on dependent services — faster, but a virtualised service can drift from the real one, so the contract is the check that keeps it honest.
- How I verified it
- Shared regression checks run before the release review, and the review itself asks for scope, test evidence, open risks, and the decision with its reason. Once squads could test in parallel, the cross-team integration test cycle went from about two weeks to about three days.
- Example
- A journey can pass inside one application and still fail at the handoff — for instance, a field the next application expects is missing or formatted differently. The shared checks catch that before the release review.
- Outcome
- Post-release incidents down 50% through pre-release validation of integrated journeys.