The quickest place to check is the Dashboard of your app in Play Console, which shows your progress toward the closed testing requirement while the test runs. Treat it as a guide, not the only record: the number of people on your email list or in your Google Group is not the number who opted in, so keep your own roster of who accepted and when. On the day you apply, you need at least 12 testers who have been opted in continuously for the preceding 14 days.
Why the list size is not the count
Google's rule is about testers who are opted in, not testers who are invited. The requirement says you must run a closed test "with a minimum of 12 testers who have been opted in continuously for at least 14 days" (App testing requirements).
Adding 30 addresses to an email list, or adding a Google Group with 30 members, only gives 30 people permission to join. Each one still has to open the opt-in link and accept. If you're unsure where that link is, see where to find the opt-in link. What counts as an opted-in tester covers the definition in detail.
So there are really three numbers:
| Number | What it tells you | Where you see it |
|---|---|---|
| Invited | People allowed to join | Your email list or Google Group |
| Opted in | People who accepted the invitation | Play Console progress on the Dashboard, plus your own roster |
| Opted in for 14 straight days | People who count when you apply | Your own dates, checked against Play Console |
Checking in Play Console
- Open Play Console and select the app.
- Go to the Dashboard.
- Find the section about the closed testing requirement and production access. In current versions of Play Console, it lists the steps (run a closed test, get at least 12 testers opted in, test for 14 days) with your progress.
- If the 12-tester step isn't marked as met, fewer than 12 testers have opted in so far, or the track isn't live yet.
Google doesn't document this screen in its help pages, so labels and layout may differ from what you see, and Google may change them. If you can't find a progress indicator, use the cross-checks below.
Check the track is live first
Testers can't opt in to a track that isn't published. Go to Test and release > Testing > Closed testing, open your track and confirm the release is live for testers. If you still have changes waiting in Publishing overview, nobody can join yet, and a count of zero is expected. Our article on why a tester invite isn't approved covers the "Send" step people often miss.
Cross-checks that don't depend on one screen
Keep a roster
A simple spreadsheet beats guesswork. One row per tester:
- the Google account you added
- the date they told you they opted in
- whether they installed the app
- notes (left, rejoined, switched phones)
Ask each tester to confirm by message once they have accepted the invitation. If they rejoin after leaving, write down the new date, because "if a tester opts out and opts back in later, the 14 days must be consecutive to count."
Compare the roster with Play Console
If your roster says 14 people joined but Play Console shows fewer, the usual reason is that someone accepted with a different Google account than the one you invited. That person isn't counted as your tester. Confirm the exact address with them, and have them accept the invitation again while signed in with the invited account.
Other common gaps:
- A tester stopped before the last step. Opening the link isn't enough; they must accept.
- Their country isn't on the closed track, so they likely can't get the test.
- They left the program while cleaning up their phone.
Look for signs of activity
Opted-in testers who use the app leave traces. Private feedback appears under Monitor and improve > Ratings and reviews > Testing feedback, and your own analytics or crash reporting will show activity from test builds. These don't give an official count, but they tell you whether your testers are actually using the app. Google can ask for more testing because of "insufficient tester engagement during the testing period", so activity matters too.
When to check
- Day 0, after publishing: confirm the track is live and the first testers can join.
- Each day until you reach 12: your 14 days effectively start when the 12th tester opts in. The closed testing timeline shows how this plays out.
- Every few days during the test: catch dropouts early, while you still have time to add people.
- The day you apply: the rule is checked at that moment. "At least 12 testers must be opted in to your closed test when you apply for production access, and they must have been opted in continuously for the preceding 14 days."
If you're below 12
- Find out who is missing by comparing your roster with the count.
- Fix account mix-ups first; they're the fastest to solve.
- Add more testers to the list and send them the link. Recruiting a few more than 12 gives you a buffer.
- Recalculate your earliest application date. A tester who joins today needs 14 consecutive days from today.
Don't remove testers from the list during the test unless you have to. Taking someone off the list may remove their access and break their streak.
Key takeaways
- Invited is not opted in. Your list size isn't your count.
- Play Console's Dashboard shows progress toward the requirement, but keep your own roster with dates.
- A mismatch between roster and Play Console usually means a wrong Google account.
- Check again on the day you apply, and aim for more than 12.
When the count and the 14 days are in place, our production access guide covers the application. If you'd rather not track a roster yourself, GoPlayTester supplies 12+ real testers who stay opted in for the full 14 days; Google still makes the final decision. You can order here.
