TestLoopers
ENEN
HomeTesting guide
PLAY CONSOLE • THE PRACTICAL GUIDE

From closed testing to a confident launch.

A clear, honest walkthrough of Google Play closed testing — from building your tester list to collecting genuine feedback and preparing your application for release.

Start your projectView the 5 steps
12real opted-in testers, where required
14continuous days, where required
05clear steps to follow
01
STEP / 01

Prepare a closed-testing track

Set up your application in Play Console, open Test and release → Testing → Closed testing, create or manage a track, and upload a usable Android App Bundle. Choose your release countries and review access settings.

Do not confuse internal testing with the closed test required for certain personal developer accounts.
02
STEP / 02

Invite real testers

Add eligible, consented testers to an email list in your Closed testing track, or use Google Groups. TestLoopers can export consenting tester addresses from your project; you still manage access in Play Console.

A TestLoopers assignment is not a Google Play opt-in. Never add an address without appropriate consent.
03
STEP / 03

Share the official opt-in link

Publish your closed-test release and provide the official opt-in invitation link to testers. Each tester must enroll using their own Google account.

The opt-in link may not be displayed until the release is published. A pasted link alone does not enroll anyone.
04
STEP / 04

Run genuine testing

Ask your testers to use the application, explore relevant flows and send honest private QA/UX feedback. Use FixLoop to document bugs and verify fixes in later builds.

TestLoopers check-ins and diaries are self-reported. They do not independently prove continuous participation in Google Play.
05
STEP / 05

Apply for production access

When Play Console confirms that your account meets its testing requirements, apply for production access. Answer Google’s questions accurately using real evidence, including issues addressed and meaningful testing changes.

Google alone decides whether to grant production access. The 12-tester/14-day threshold does not guarantee approval.
FINAL REVIEW

Pre-launch checklist

Use this quick list to review your setup. These checkboxes are local to this page and do not verify Play Console enrollment.

0 / 5

COMMON QUESTIONS

Frequently asked questions

Does every developer need 12 testers for 14 days?

No. Google’s stated requirement applies to personal developer accounts created after 13 November 2023. Check your own account status in Play Console.

Does TestLoopers automatically confirm Play Console opt-ins?

No. TestLoopers tracks assignments and self-reported testing activity. Developers must verify opt-ins and continuity in Google Play Console.

Can testers earn money for opting in or reviewing an app?

No. Store installs, opt-ins, ratings and reviews are not rewarded. Only separately funded, approved genuine private QA/UX work can carry a reward.

Google testing requirements Set up a closed test

Ready to organize your first real test?

Bring genuine testers, meaningful QA feedback and documented fixes into one workspace.

Create your project