How Vitality Global Cut Test Cycles from 4 Days to 4 Hours

Overview

Vitality Global operates the world's leading behavioral engagement wellness platform, serving millions of members across more than 20 markets. Behind it sits a global technology team of more than 400 professionals, with engineering and quality assurance spread across several countries.

The platform rewards members for healthy choices and tracks millions of events each week across health, driving, and spending goals. Nearly all of that reaches members through one app, the Vitality Global Wellness App, which integrates Vitality Health and is built and maintained entirely by an in-house team of engineers.

That puts a great deal of weight on a single app. It handles health and financial data, which puts it under strict privacy regulations, and it has to run just as well on an older, low-cost handset as on the latest flagship phone. Both things had to be true at once, and the testing setup the team had been using could not reliably deliver either.

Shared Device Infrastructure Was Limiting Test Reliability

Vitality Global had moved away from maintaining an in-house device lab some time ago. Mobile testing, covering UI validation, functional validation, and performance benchmarking, ran on a third-party device farm that provides remote access to real phones.

Because those devices were shared across multiple customers, conditions varied from one run to the next. Devices were not always returned to a clean state between sessions, and network connectivity was simulated rather than delivered over a live mobile network. Both introduced failures unrelated to the application itself. Combined with the range of Android devices and operating system versions across Vitality's key markets, this left the team with results it could not consistently reproduce.

Device coverage also carried an ongoing operational cost. Each new handset model and OS version in a growing market required additional devices to source, configure, and maintain.

The wider effect was on confidence in the test suite. Where failures cannot be reliably attributed to the application, teams start discounting them, and genuine defects risk being deprioritized alongside false positives. A full test cycle also took four days, which limited how often the team could release and left open questions at the point of sign-off.

Why TestMu AI Private Devices Rather Than More Shared Ones

Vitality Global chose TestMu AI's private devices, meaning physical phones reserved exclusively for its own teams, for three reasons a shared pool could not address.

• Meeting privacy regulations. Vitality Global operates under POPIA, South Africa's data protection law. Running tests on dedicated, isolated devices means member data never touches infrastructure shared with anyone else, which keeps testing inside the boundary regulators expect.
• Phones always available. Because the devices are permanently reserved, there is no waiting in a queue behind another company. Teams can run many tests side by side, at any hour.
• Testing on real mobile networks. Private devices can hold actual SIM cards and connect through Vitality's own secure network. That lets the team test what happens on a real mobile connection, which a simulated network cannot reproduce.

Together, these gave Vitality Global a testing setup that fits how the business is regulated, rather than one it had to work around.

A Dedicated Device Pool That Mirrors the Production User Base

Vitality Global now runs a permanently reserved pool of private devices on the TestMu AI cloud, split evenly between Android and iOS to mirror its production user base rather than lab convenience. The pool includes dedicated Samsung Galaxy clusters spanning premium S series through mid-range A series handsets, alongside Apple iPhones.

QA teams in South Africa, India, and the United Kingdom all work from the same pool. Day-to-day manual and exploratory testing runs alongside scheduled automation, which executes the regression suite across the same private devices for close to 20 hours a day.

Automation coverage now exceeds 85% across both legacy and flagship devices, and test cycles that previously took four days complete in under four hours.

A Failed Test Now Means a Real Problem

The change the engineering team notices most does not show up in a metric.

Because the devices are theirs alone, the background noise is gone. When a test fails now, it points to something genuinely wrong with the app. And because the phones use real SIM cards and a secure network connection, the team catches issues that only appear on live mobile networks, such as a call or data session dropping as a phone moves between cell towers, before members ever run into them.

That has changed how QA and developers work together. Arguments about whether a failure was real have simply stopped. Developers trust the results, so testing now happens earlier in development rather than being saved until the end, and QA has become the team that clears a release with confidence instead of the one holding it up.

Not having to maintain physical phones has also given engineers their time back. That time now goes into writing better automated tests.

"The change our teams feel most is not the speed; it is the certainty. When a test fails now, we know it is telling us something real about the application, and that has changed how our QA and development teams work with each other."

Zayd Mahomed, Chief Technology Officer, Vitality Group Inc.

From a Monthly Gamble to a Weekly Release

The release schedule tells the story most clearly. Vitality Global has gone from releasing monthly, which the team describes as a gamble, to releasing every week, with mobile network checks built directly into the automated pipeline that ships new code.

For a platform managing health, driving, and spending behavior for millions of members across more than 20 markets, that pace is the difference between fixing member problems after they happen and stopping them before they start. Testing now keeps up with the business, and it does so within the privacy rules the business has to follow.

Ready to improve your testing? Schedule a demo to see how TestMu AI can help your team achieve similar results.