Short answer: after you roll out a closed testing release, Play Console gives you an opt-in URL. Each tester opens it while signed in with the Google account on your tester list, taps to become a tester, then installs the app from Google Play. Most problems come from the wrong Google account, a country not in the release, or testers who skip the opt-in step.
Where to find the link
In Play Console, open your closed testing track and go to the testers section. The opt-in link appears once the release is rolled out and the tester list is saved. Copy the web link, which works on desktop and on phones.
Instructions to send testers
Copy this into your tester brief:
- Open the link on your phone or computer, signed in with the Google account you gave me.
- Tap Become a tester and wait for the confirmation.
- Tap the Google Play link and install the app.
- Please stay opted in and keep the app installed for at least 14 days.
- Send feedback through Google Play or the form I shared.
Common problems and fixes
"App not available"
The tester's account may not be on the list, or their country may not be included in the release. Check both.
The tester has several Google accounts
Play uses the account active in the Play Store app. Ask them to switch accounts in the Play Store, or add the account they actually use.
Tester installed but isn't counted
Installing from a shared APK skips opt-in. They must opt in through the link and install from Google Play.
Changes to the list don't show yet
Give it a little time after saving. Then ask the tester to open the link again.
Log opt-in dates
Because the 14 days must be continuous, record each tester's opt-in date. A screenshot of the confirmation page is simple proof for your own records and helps you spot who to check on.
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
Can testers opt out?
Yes, from the same link. If they opt out before 14 days, they no longer count, and rejoining restarts their clock.
Do testers see the app on the public Play Store?
Only testers who opted in can install the closed build.
Can I use a Google Group instead of emails?
Yes. Testers who join the group can then use the opt-in link.
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)