Checklist

Closed Testing Checklist

23 things to do before, during, and after your Google Play Closed Testing period. Print this, check off each item, and avoid the mistakes that get developers rejected.

Phase 1: Before You Start (Pre-Launch)

Create a Google Play Console account ($25 one-time registration fee). Verify your identity — this can take 1-2 days.Build your app as an Android App Bundle (.aab), signed with a release keystore. Debug-signed builds are rejected at upload.Prepare your store listing — app name, short description, full description, screenshots, icon, feature graphic. It does not need to be final, but it must comply with Google's policies.Add a privacy policy URL in your store listing and within your app. Missing privacy policy is a common policy rejection.Integrate analytics (Firebase Analytics recommended). You need engagement data to monitor testers and answer the production access questionnaire.Remove debug-only content — debug toasts, placeholder text, developer menus. Testers should see what real users will see.Recruit 14-15 testers (not 12 — build in a buffer). Verify each has a physical Android device and unique Google account.Set up a communication channel — Discord server, WhatsApp group, or email thread for daily check-ins and feedback collection.

Phase 2: Setup & Launch (Day 0-1)

Create a Closed Testing track in Play Console: Testing > Closed Testing > Create track.Upload your .aab file to the track.Set country availability to include every country where your testers are located. If a tester's country is not listed, they cannot access the app.Configure tester access — email list or Google Group. Generate the opt-in link.Start rollout. The 14-day clock begins when the track status shows "Available" or "In review."Share opt-in link with all testers immediately. Confirm 10+ installs within the first 24 hours.

Phase 3: Active Testing (Days 1-14)

Send daily engagement reminders to all testers. Same time every day builds habit.Monitor active tester count daily. If you drop below 12, replace inactive testers immediately.Collect feedback actively. Ask specific questions: "Did anything break today? What was confusing?"Document all feedback — screenshots, timestamps, device models, Android versions. You will need this for the production access questionnaire.Deploy at least one update by day 6 addressing feedback. A second update by day 10 is even stronger.Check Play Console Android Vitals weekly for crash rates and ANR rates. Fix any issues within 24 hours.Announce updates to testers. "I just pushed an update fixing the crash on Galaxy A54. Please update and confirm it works."

Phase 4: Production Access (Day 15+)

Wait until day 15 or 16 before applying — engagement data takes time to sync.Compile evidence: feedback screenshots, changelog, analytics dashboard export, Play Console Statistics screenshot.Answer the production access questionnaire with specific details: bugs found, fixes deployed, tester devices, dates, versions.Submit application and await Google's decision (typically 1-3 business days).

Quick reference: requirements at a glance

Testers

12-15

Real people, real devices, unique accounts

Duration

14 days

Calendar days, weekends and holidays count

Updates

1+

Deploy at least one update based on feedback

Need testers to check off your list?

Get 12 verified testers matched within 24 hours. Check off the hardest item on your checklist and focus on building your app.

Get 12 Testers Now→From $14.99