Google Play Closed Testing Checklist

Use this checklist to ensure you have covered everything before, during, and after your Closed Testing period. Missing one item could mean restarting your 14-day clock.

1

Before you start testing

Confirm your developer account is verified and has no policy violations.Upload a functional, stable build to the Closed Testing track — not a placeholder.Create a clear opt-in link or email list in Google Play Console.Set up a feedback channel (email, form, or in-app) so testers can report issues.Recruit at least 14 testers (12 minimum + 2 buffer for dropouts).Ensure every tester uses a unique Google account with a real Android device.Verify that no two testers share the same device or IP address.Send each tester the official Play Store opt-in link — do not sideload APKs.

3

During testing (Days 1-14)

Confirm all testers have installed the app from the Play Store via your opt-in link.Monitor tester engagement daily — Google tracks app opens and session duration.Prompt inactive testers. Anyone who does not open the app for 48+ hours may not count.Replace any testers who drop out. Maintain 12+ active testers at all times.Monitor crash rates in Play Console or Crashlytics.Collect and document all feedback systematically.Fix critical bugs quickly — a crashing app will lead to rejection.Push minor updates if needed. This shows active development.

4

After testing (Production access)

Verify your Closed Testing track shows 14+ consecutive days with 12+ active testers.Confirm all major bugs reported during testing have been fixed.Review your store listing one final time for completeness and accuracy.Verify your app complies with all Google Play Developer Program Policies.Ensure your app does not request unnecessary permissions.Submit your production access application in the Play Console.If rejected, read Google's feedback carefully and address every issue before restarting.

The one item most developers miss

The most commonly overlooked item is tester engagement monitoring. Many developers assume that as long as 12 people install the app, they are good. Google tracks whether testers actually use the app. If a tester installs and never opens it again, they may not count.

Check your tester engagement daily. If someone has not opened the app in 48 hours, reach out and encourage them to use it. If they remain inactive, replace them. TesterBee handles this monitoring for you so you can focus on building your app.

Pre-testing preparation checklist

Before a single tester opts in, these items should be complete. Starting testing without these in place is the most common cause of first-attempt rejections:

Post-testing verification checklist

After 14 days of testing, verify these items before clicking submit on your production access application:

Frequently asked questions

Do I really need to complete every item on this checklist?

Not every item is a hard requirement, but each unchecked item increases your rejection risk. The checklist is based on the most common rejection reasons reported by developers. Think of it as risk reduction — each item you complete lowers the probability of a rejection and another 14-day wait.

What is the single most important item on the checklist?

Tester authenticity and engagement. Google can forgive an incomplete store listing (they will tell you to fix it), but they will not forgive fake testers or a testing period where no real engagement occurred. If you only focus on one thing, make it the quality of your testers and their engagement.

Can I update my store listing after submitting my production access application?

Yes, you can update your store listing while your application is under review. However, significant changes may trigger an additional review delay. Make your listing as complete as possible before applying, then make only minor updates during the review period.