TestLabs

TestLabs runs your app on real Android phones rather than emulators. The device pool mixes mid-range and high-end models, so compatibility problems tied to specific chipsets or screen sizes show up the way they would on a user's phone. Setup is handled by the service once you share your package ID.

The service is built around one specific Google Play rule: a closed test with at least 20 testers for 14 consecutive days. TestLabs manages the testers and the schedule so the app compliance testing finishes inside the window Google checks, which is the whole reason most developers sign up.

Testing runs for the full 14 days Google requires, not a shortened trial. Daily runs mean the app is exercised repeatedly across the window, which matters for catching issues that only appear after sustained use or on a cold start days into a test cycle.

Every plan includes test logs for debugging, screenshots of issues and test scenarios, and notes on performance, responsiveness, and errors. That evidence is useful both for fixing bugs and for showing a client or teammate that the closed test actually ran.

There's no cap on the size of the app under test. Lightweight utilities and data-heavy games go through the same process, so studios don't have to trim assets or ship a stripped build just to get it tested.

You can follow the run in real time through logs and progress reports instead of waiting blind for two weeks. Live updates make it easier to tell whether the closed test is on track and to plan the release date.

Pricing is split into three tiers rather than a subscription, and the entry point is low. You can also test more than one app by buying separate slots, which suits developers managing several releases at once.