BLOG
BlogGuides

Mobile release testing: a guide for app teams

For iOS and Android teams: tests that survive a redesign, App Store review, builds for CI, an agent that tests its own build, and the states other tools miss.

What mobile teams told us they fight#

Every mobile testing survey and vendor pitch opens on the same problems: suites that break when screens change, too many devices and OS versions, sign-up codes nobody automates, and native builds that make CI slow. Shopify's mobile team described a suite that kept failing while the app was fine; Apple says over 40% of unresolved review issues fall under guideline 2.1, app completeness.

These posts cover each of those with plain-language tests that run on iPhone, iPad and Android, and real runs where we have them.

Write tests that last#

Get the release out#

Builds and CI#

The parts other tools cannot reach#

The mobile series has a real run for each, with frames, the result and the review video: permission prompts, notifications, SMS codes, deep links, Face ID, the app killed in the background, crashes, the network and battery, rotation and dark mode, location, Live Activities, and OS versions. Start with The hardest parts of mobile app testing, each one run for real.

Start with your next build#

Upload it, write the journey your users take first, and run it on a phone and a tablet. App tests are on every plan, the free trial too: 10 runs, no card.

Filed underiPhone and iPadAndroidReleases and regressions