Portfolio

Gaming · QA vendor transition in 2 weeks with zero untested releases

Growing operational friction and inconsistent testing outcomes led the developer of a gaming marketplace to engage a new QA vendor with no disruption to regular business processes. a1qa seamlessly assumed full QA ownership and ensured failsafe software operation.
Functional testing
Media and entertainment
Regression testing

Project overview

The handover was fast, and nothing slipped through. Our releases kept shipping while the switch happened.

Head of QA

The client developed a digital games and content marketplace. They needed to change QA vendors because of timing overlaps and quality problems in their previous engagement while ensuring the transition would not disrupt their release cadence.

The challenge

The client was already shipping software on a regular schedule, which could not be interrupted by a vendor change. The prior relationship had two problems: work timings that overlapped in ways that slowed delivery, and quality issues in the testing itself. Any new setup had to take over the full release testing scope quickly, keep the existing standard of release suite test coverage intact, and ensure that nothing went live untested during the transition. The margin for a quiet drop in release suite coverage was zero.

Services offered

Functional testing
Regression testing

Project scope

The client worked to a continuous deployment schedule, so the transition had to fit around live shipping rather than interrupt it. a1qa staffed the engagement to match the outgoing setup, taking on the same release testing scope previously handled by a team of two.

Because the marketplace shipped games and digital content on a rolling basis, any pause in testing would have meant either a stalled release train or a batch of untested builds reaching users, and neither was acceptable to the client.

The delivery model was a full ownership transfer: a1qa absorbed the complete release testing responsibility rather than running a parallel or shadow arrangement. This meant a1qa took direct accountability for every release check from the moment ownership moved, instead of splitting duties with the outgoing setup and leaving room for gaps between the two. The whole process involved the following phases:

  • Phase 1: Discovery. Before taking anything over, a1qa mapped the test coverage of the existing release suites, recording which functional areas and regression checks each suite exercised. This step made the prior scope explicit so that nothing could be quietly dropped once the handover started. It also gave a clear baseline of what “the standard” meant in practice, turning an informal understanding of the previous team’s work into a documented reference the client could inspect. With that baseline in hand, both sides agreed on what “no coverage gap” would mean before a single test moved across.
  • Phase 2: Pilot. a1qa began running release testing work against the mapped suites while the outgoing setup was still in place, checking that results matched the established standard before full responsibility moved across. Running in parallel against known suites let a1qa confirm its functional and regression testing produced consistent results before the client committed to the switch, so the handover started from evidence rather than assumption.
  • Phase 3. Full release testing ownership was taken over within a two-week window. Throughout this period, the client kept shipping software on schedule, and each update was tested rather than shipped blindly. As ownership moved suite by suite, a1qa ran the functional and regression checks captured during the Discovery phase so that the release suite coverage the client relied on stayed in place while the handover was completed.
  • Phase 4. With ownership settled, a1qa continued to run the release suites at the release suite coverage level captured during the Discovery phase, holding the prior standard steady through and after the switch. The engagement moved into steady-state delivery, with a1qa owning the functional and regression testing for each scheduled software rollout and reporting results through the client’s existing tracking, so the team kept the same visibility they had before the vendor change.

Across these phases the goal was continuity, not expansion: the release suites were maintained at their existing functional and regression coverage rather than broadened, so the client kept a predictable, tested go-live flow throughout the change. Keeping scope fixed also made the handover measurable, since the mapped Discovery baseline gave a single reference point to check every later phase against.

 

Technologies & tools

  • Java
  • TestNG
  • Jenkins
  • TestRail
  • Jira
  • REST clients

Project results

  • Full release testing ownership moved to a1qa without a break in the client’s release schedule.
  • Functional and regression coverage of the release suites was held at the prior standard through the switch, with no quiet drop in scope.
  • The release suite coverage mapping done before takeover meant the client could see exactly what was being tested at every phase of the handover.
  • No release was shipped untested while the QA vendor transition was in progress.

Project in numbers

2
weeks to take over full release testing ownership
2
QA team members’ scope transferred to a1qa
0
releases shipped untested during the switch

Get in touch

Please fill in the required field.
Email address seems invalid.
Please fill in the required field.
We use cookies on our website to improve its functionality and to enhance your user experience. We also use cookies for analytics. If you continue to browse this website, we will assume you agree that we can place cookies on your device. For more details, please read our Privacy and Cookies Policy.