Short answer: Google's closed testing requirement is written for personal developer accounts created after November 13, 2023. If your account is personal and newer than that date, you need a closed test with 12 or more testers opted in for 14 continuous days before production. Here's how to tell which situation you're in and how to choose an account type for the right reasons.
Why the account type matters
Google's help article is titled "App testing requirements for new personal developer accounts" and describes the rule only for personal accounts created after November 13, 2023. Production and Pre-registration stay disabled for those accounts until they meet the testing requirement and apply for production access.
So the first question isn't "how do I find testers?" It's "does this apply to me?"
How to check your own account
Open Play Console and look at the account details to see whether it's registered as personal or organization, and when it was created. Then check the app's Dashboard. If you see tasks about running a closed test before you can publish, the requirement is active for you.
Choosing an account type for the right reasons
Personal accounts
They suit individual developers, hobby projects and solo founders without a registered company. Expect the closed testing step and plan two to three weeks for it, plus review time.
Organization accounts
They are for registered businesses and need organization verification details. Register one when you are genuinely publishing as a business, because that's what the account represents to users and to Google.
Don't switch account types only to avoid testing. A real closed test gives you crash reports, usability feedback and fixes before your first public review, which helps your app regardless of the rule.
If you already have a personal account
Use the time well. Start the closed test as soon as app setup is complete, and use internal testing for quick builds before that. Recruit a buffer of testers, keep a log of opt-in dates, and plan at least one update during the test. TestLancer has a longer explainer on personal vs organization accounts.
What changes after production access
Once Google approves your application, Production and Open testing unlock. You can keep using closed testing for future updates, which Google recommends to reduce low ratings when you release changes.
The official rules, in one place
According to Google's Play Console Help article on app testing requirements for new personal developer accounts:
- The rule applies to personal developer accounts created after November 13, 2023.
- You must run a closed test with at least 12 testers who have been opted in continuously for at least 14 days.
- Production and Pre-registration stay disabled until you meet the requirement; you then apply for production access from the Dashboard.
- The application has three parts: About your closed test, About your app/game and About your production readiness.
- Review usually takes seven days or less, but can take longer. If engagement was too low or you had fewer than 12 opted-in testers, Google may ask you to keep testing.
- Testers who opt out before 14 days don't count, and if someone opts out and back in, their 14 days must be consecutive.
Quick checklist before you apply for production access
- [ ] At least 12 testers opted in today, each for 14 or more days in a row (check your log, not your memory).
- [ ] A buffer of extra testers in case someone drops out at the last minute.
- [ ] Notes on which features testers used, and whether that matched how you expect real users to behave.
- [ ] A short summary of the feedback you received and how you collected it (Play testing feedback, a form, a chat group).
- [ ] A list of changes you made because of the test, with version numbers.
- [ ] Working test credentials in Play Console if your app needs a login.
- [ ] Content rating, target audience and data safety answers that match the real app.
- [ ] No crashes or empty screens on the build you're about to ship.
If any box is empty, a few more days of testing usually costs less than another review cycle.
Mistakes that cost developers extra weeks
- Recruiting exactly 12. One opt-out and you're back to waiting.
- Running the test on the internal track. Internal days don't count toward the requirement.
- Sharing an APK instead of the opt-in link. Testers must opt in and install from Google Play.
- Tidying the tester list mid-test. Removing someone ends their streak.
- Shipping no updates. The production readiness section asks what you changed because of testing.
- Using friends who never open the app. Google can ask for more testing when engagement is low.
- Buying reviews or ratings. They break Google Play policy and give you nothing to report. TestLancer never sells them.
FAQ
My personal account is from 2022. Does the rule apply?
Google's article describes the requirement for personal accounts created after November 13, 2023. Check your Dashboard to confirm what Play Console asks of you.
Can I transfer apps to an organization account later?
Google Play has an app transfer process. Check Play Console Help for the current steps before you plan around it.
Does an organization account need testing at all?
Testing is still a good idea for every app, even when it isn't a gate to production.
Next step
If you can't find 12 reliable people on your own, TestLancer's Google Play closed testing service runs a 14-day closed test with real testers who opt in, use your app and send feedback you can summarise in your production access application. You can also use the free Google Play Launch Center checklist first. TestLancer does not sell reviews, ratings or installs, and no one can guarantee Google will approve production access. Your app still has to meet Google Play policy.
Top comments (0)