Free tool

Google Play closed testing checklist for 12 testers and production access.

A practical runbook for preparing the release, coordinating 12+ testers, surviving the 14-day window, and turning tester feedback into a stronger production-access application.

12minimum opted-in testers

14continuous testing days

15safer tester target with buffer

How to use this pageCheck off each item as you complete it. The tracker is saved only in this browser, so you can use it as a lightweight launch handoff without creating another account.

Your saved progress

0 of 20 checks complete

Progress is saved in this browser. No account required.

0%

01

Prepare the release

Before upload

Make the build testable before you spend a day recruiting testers. Broken installs and missing policy surfaces create avoidable delays.

Confirm the requirement applies to your accountThe 12-tester rule applies to new personal developer accounts created after 13 November 2023.Complete the core Play Console setupFinish app content, target audience, store listing basics, and required declarations.Upload a stable release candidate to closed testingInternal testing helps with smoke tests, but it is not the qualifying closed-test track.Prepare privacy, support, data safety, and test credentialsGive testers and reviewers a clear contact path and working login details when needed.Smoke-test install, onboarding, login, and the main taskUse a real Android device and fix crashes, blocked screens, and broken permissions before inviting people.

02

Start the window

Closed test setup

Your count is a floor, not a plan. A small buffer protects the start date when someone cannot install or accidentally opts out.

Create or select a closed testing trackIn Play Console, use Testing → Closed testing and roll out the release there.Prepare the tester email list or Google GroupCheck that every address uses a Google account that can access the test.Invite at least 12 testers — 15 is a safer targetKeep a buffer above the minimum in case a tester leaves or loses access.Check countries, device support, and install availabilityAsk testers to confirm that the opt-in link and install path work for them.Send a test brief and one feedback channelTell testers what to try and remind them to stay opted in continuously for 14 days.

03

Collect evidence

During the 14-day window

The strongest closeout is specific: what testers tried, what broke, what changed, and how you verified the fix.

Check the opted-in count throughout the windowIf a tester opts out and later opts back in, that time is not one continuous qualifying period.Give testers realistic feature tasksCover onboarding, the main value flow, payments, notifications, offline states, or other critical paths.Log feedback with device and build contextRecord device, Android version, app version, steps to reproduce, and severity.Review crashes, ANRs, and the pre-launch reportA healthy tester count does not make a release ready if the app is unstable.Ship fixes deliberately and retest themDocument what changed in each build and ask testers to verify the affected flow again.

04

Apply with evidence

Before production access

Do not reconstruct the story on day fourteen. Keep notes as you go so the application reflects the real test.

Confirm 14 continuous days and 12 opted-in testersUse the status shown in Play Console as the source of truth — not only your upload date.Summarize recruitment, engagement, and feedbackNote how testers were recruited, what they used, and how feedback was collected.Document changes made from the closed testList fixes or UX improvements and explain how you verified them.Recheck production readiness and policy complianceYour current release, listing, screenshots, privacy policy, and data safety answers should agree.Apply from the Play Console dashboardAnswer the closed test, app, and production-readiness questions in your own words.

What matters beyond the count

Google wants to understand the quality of the test.

How testers were recruited and whether they could install the release
Which features testers used and how closely that matched expected users
What feedback you received, what you changed, and how you verified fixes
Whether the app is stable, policy-ready, and accurately represented in the listing

1

Day 0

Launch cleanly

Verify the opt-in path, release availability, and starting count.

2

Days 1–3

Find blockers

Prioritize onboarding, login, and the main task before testers lose momentum.

3

Days 4–13

Broaden coverage

Exercise edge cases, collect device context, and retest important fixes.

4

Day 14+

Close out

Confirm Play Console status, write evidence-based answers, and keep testing during review.

For the current account-specific rules and application questions, check Google Play’s official testing guidance. Completing a checklist does not guarantee production access.

Closed testing checklist FAQ

Does this checklist guarantee production access?

No. It helps you prepare a stronger closed test, but Google still reviews your app, policy readiness, and production-access request.

Should I keep more than 12 testers?

Yes. A buffer above 12 helps if a tester leaves, cannot install, or does not complete opt-in correctly.

Can I use this for client apps?

Yes. Agencies can use it as a handoff checklist before inviting testers or requesting production access.

Need the tester side handled too?

Move from checklist planning into managed tester coordination, opt-in tracking, and feedback collection for your Android launch.

Get real testers