Why This Guide Exists
When I set up closed testing for the first time, I clicked around Google Play Console for two hours. The interface is confusing. The documentation is scattered across 17 different help articles. And none of it is designed for someone who just wants to get their app tested and approved.
I eventually figured it out, but it took way longer than it should have. This guide is what I wish I'd had: a single, complete walkthrough from "I have an APK" to "my testers are actively using my app."
Following this guide start to finish: 30-45 minutes (assuming you already have your APK/AAB file ready).
What You'll Need Before Starting
Before you open Google Play Console, make sure you have:
- Google Play developer account (the $5 one-time fee must be paid)
- Your app's APK or AAB file (Android App Bundle is recommended)
- App icon (512x512 PNG, no transparency)
- At least 2 screenshots (phone screenshots are required; tablet optional)
- Privacy policy URL (if your app collects any data)
- List of tester email addresses (at least 15-20 to maintain buffer)
If your app requests sensitive permissions (location, camera, contacts, etc.) or collects user data, you must have a privacy policy. Google won't let you proceed without one. Use a free generator like TermsFeed if you don't have one yet.
Step 1: Create Your App in Play Console
Log into Google Play Console and click "Create app" in the top right.
You'll be asked:
Check the declarations, then click "Create app".
Step 2: Set Up Your Store Listing (Minimum Requirements)
Before you can create a testing track, Google requires you to complete some of your store listing. You don't need everything perfect, but you need the minimums.
Go to Main store listing in the left sidebar and fill out:
Required Fields
- App name: Already filled from Step 1
- Short description: 80 characters max, appears in search results
- Full description: Up to 4000 characters, explain what your app does
- App icon: 512x512 PNG (must be uploaded)
- Feature graphic: 1024x500 JPEG/PNG (optional but recommended)
- Phone screenshots: At least 2, up to 8 (JPEG/PNG, 16:9 or 9:16 ratio)
- Category: Choose the most relevant app category
Click "Save" at the bottom. Don't worry about perfection here—you can refine this before production. We just need the basics to unlock testing.
Step 3: Complete the Content Rating Questionnaire
Go to Content rating in the left sidebar. Click "Start questionnaire".
This questionnaire determines your app's age rating (Everyone, Teen, Mature, etc.). Answer honestly—lying here can get your app suspended.
Common questions:
- Does your app contain violence? (Cartoon violence counts)
- Does it have user-generated content or social features?
- Does it contain romantic themes or nudity?
- Does it reference drugs, alcohol, or tobacco?
After completing the questionnaire, click "Calculate rating". Google will assign age ratings for different regions (ESRB, PEGI, etc.).
Most simple utility apps get "Everyone" rating. If you're unsure about a question, be conservative and disclose more rather than less. You can always update this later.
Step 4: Fill Out the Data Safety Section
This is critical and trips up most developers. Go to Data safety in the sidebar.
Google wants to know:
- Does your app collect or share user data?
- What types of data (location, contacts, personal info, etc.)?
- How is that data used?
- Is data encrypted in transit?
- Can users request data deletion?
If you use Firebase Analytics, AdMob, Facebook SDK, or any third-party analytics—you ARE collecting data. Don't select "No data collected" unless your app is truly offline with zero SDKs. Lying here will result in rejection or suspension.
Common data types you need to declare if using popular SDKs:
Once you've declared all data types, click "Save".
Step 5: Create Your Closed Testing Track
Now we get to the actual testing setup. In the left sidebar, go to Testing → Closed testing.
Click "Create new release".
Upload Your App File
You'll see a section to upload your APK or AAB file. Click "Upload" and select your file.
Wait for the upload to complete. Google will scan your file for malware and policy violations. This usually takes 2-5 minutes.
Fill Out Release Details
Once uploaded, you'll need to provide:
- Release name: Something like "v1.0 Closed Testing" (for your reference only)
- Release notes: What testers should know (e.g., "Initial testing version - please check login flow")
Click "Save" (do NOT click "Review release" yet).
Step 6: Create a Tester List
Before you can start testing, you need to tell Google who your testers are.
In the Closed testing section, find the "Testers" tab.
Click "Create email list".
Setting Up Your Tester List
Something like "Closed Test Group" or "v1.0 Testers"
Paste email addresses, one per line. These MUST be Gmail addresses or emails associated with Google accounts.
Click "Save changes" to create your tester list
Add 18-20 email addresses even though you only need 12. This gives you a safety buffer in case some testers don't accept the invite or drop out during the 14-day period.
Step 7: Review and Start Your Release
Back in the Closed testing section, you should now see your release draft. Click "Review release".
Google will show you a summary of what you're about to publish:
- App version
- Number of testers
- Release notes
If everything looks correct, click "Start rollout to Closed testing".
Your closed testing track is now live. Within a few minutes, Google will send invitation emails to all the addresses on your tester list.
Step 8: Share the Testing Link with Your Testers
Here's where many developers get confused. Google sends invitation emails, but those emails sometimes go to spam. It's better to manually share the testing link.
Go to Closed testing → Testers tab. You'll see a section called "How testers join your test".
Copy the opt-in URL. It looks something like:
https://play.google.com/apps/testing/com.yourapp.package
Send this link to your testers via:
- WhatsApp, Telegram, or Discord
- Email (send it yourself, don't rely on Google's auto-email)
- Slack or other team communication tools
Include clear instructions:
"Hi! I need your help testing my app for Google Play approval. Please follow these steps:"
- Click this link: [paste opt-in URL]
- Click "Become a tester"
- Download the app from Google Play
- Open the app at least 3-5 times over the next 14 days
- Keep the app installed for the full 14 days
Step 9: Monitor Your Testing Progress
Once testers start opting in, you can track progress in Play Console.
Go to Testing → Closed testing → Manage track → Testers tab.
You'll see metrics for:
The 14-day countdown starts when you reach 12 continuously opted-in testers. If your count drops below 12 at any point, the timer pauses or resets. This is why having extra testers is crucial.
Step 10: After 14 Days—Apply for Production
Once you've maintained 12+ testers for 14 consecutive days, the "Apply for production access" button will appear in your Play Console dashboard.
Before clicking it, run through this final checklist:
✅ Pre-Production Checklist
Once you've verified everything, click "Apply for production access" and wait 2-4 days for Google's review.
Troubleshooting Common Issues
Problem: Testers Can't Find the App on Play Store
Solution: They need to click the opt-in link FIRST, then search for your app. The app won't appear in search until they've opted into testing.
Problem: Tester Count Keeps Dropping
Solution: Testers are opting out or uninstalling. Follow up with them. Remind them it's only 14 days and their help is critical. Consider recruiting more testers immediately.
Problem: "Apply for Production" Button Not Appearing
Solution: Check that you have 12+ opted-in testers for 14 consecutive days. Also ensure all store listing sections are complete (Data Safety, Content Rating, Main Listing).
Problem: Upload Rejected Due to Policy Violation
Solution: Read the violation email carefully. Common causes: app name contains trademarked terms, icon uses Google's brand colors, permissions don't match functionality. Fix and re-upload.
Key Takeaways
- Set up your store listing basics before creating a testing track
- Data Safety section is mandatory and must be accurate
- Always add 18-20 testers even though you only need 12
- Share the opt-in link manually—don't rely on Google's auto-emails
- The 14-day countdown starts when you hit 12 testers, not when you upload
- Monitor tester engagement; low usage can still cause rejection
Setting up closed testing isn't complicated once you know the exact steps. Follow this guide, take your time with each section, and you'll have your testing track live within an hour.
Need testers who will actually stay engaged? Our testing service provides verified testers who understand the 14-day requirement.
Frequently Asked Questions
Do I need to upload my app to production before creating a closed testing track?
No. You can (and should) set up closed testing before ever submitting to production. In fact, for personal developer accounts, completing closed testing is a requirement before production access is even available.
Can I have multiple closed testing tracks at the same time?
Yes. Google Play allows multiple testing tracks (closed, open, internal). You can run a closed test while also having an internal test active. Each track operates independently.
What happens if I upload a new version while testing is active?
Your existing testers will receive an update notification. The 14-day countdown doesn't reset unless your opted-in tester count drops below 12. Updating your app during testing is completely normal and encouraged.
Written by Priya Sharma
Expert in Google Play app testing and Android development. Helping developers navigate the app approval process with practical insights and proven strategies.