Play Console closed testing setup guide

New personal Google Play developer accounts must run a closed test with at least 12 testers opted in for 14 continuous days before they can apply for production access. Google has changed this number before (it was 20 until late 2024), so confirm the current rule in the Play Console Help Center before you start.

1. Create the closed testing track

1. In Play Console, open your app → Test and release → Testing → Closed testing.
2. Create a track (or use the default Alpha), upload an AAB and complete the release.
3. Fill in the store listing, content rating, data safety and target audience — the release is not reviewed until these are done.

2. Add the Genuine Testers Google Group as your tester list

You don't need to create your own group. Every Genuine Testers tester joins one shared group, genuine-tester.

1. In the closed track, under Testers, choose Google Groups and add genuine-tester@googlegroups.com.
2. Save. Testers who join the group with their testing Gmail can then opt in.

3. Copy the opt-in link

Under Testers → How testers join your test, copy the link. It looks like https://play.google.com/apps/testing/com.your.package. Open it in a private window with a different Google account to make sure it works.

4. List the app in Genuine Testers

Paste the opt-in link into My apps → Add app. Aim for 15–16 testers: only testers who stay opted in for all 14 days count, and a few always drop out.

5. Every day

• Testers upload one screenshot of your app in use. The deadline is noon the next day in their own timezone.
• You approve or reject proofs (with a reason). Anything you don't review within 48 hours is approved automatically.
• When a tester shows up in Play Console's tester list, tap Mark as opted in on their row.

6. After 14 days

Export the PDF report from your app dashboard and use Production readiness to draft honest answers to Play Console's questions about your test: how you recruited testers, what feedback you received and what you changed. Google decides on production access — no service can guarantee it.