Closed testing vs internal testing: which one Google requires

Updated

If you have been running an internal test for two weeks and production access is still locked, this is why:

Internal testing does not satisfy the requirement. You need a closed test.

It is an easy mistake. Both tracks distribute pre-release builds to testers, both show up under Testing in Play Console, and internal testing is faster and easier to set up — so it is the one people reach for first.

The rest of the rule, who it applies to and what counts as a tester, is in Google Play's 12 testers, 14 days requirement.

The tracks, side by side

Internal testingClosed testing
TestersUp to 100, by email addressFar larger; email lists or Google Groups
ReviewSkipped or minimalFull review before it goes live
Speed to testersMinutesHours to days on first submission
Opt-in linkYes, for named testersYes, shareable with your tester list
Counts toward production accessNoYes

The last row is the only one that matters for your immediate problem.

Why Google draws the line there

The requirement exists to make sure an app has been in front of a genuine group of people before it reaches the store. Internal testing is deliberately frictionless: up to 100 addresses you type in yourself, no meaningful review. That is exactly what you want for your own team, and exactly what you would use to trivially satisfy a requirement if it counted.

Closed testing goes through review and is built around a real tester list. It is a weaker signal than a public launch and a much stronger one than emailing yourself.

Switching over

If you have been on the wrong track, you have not lost your work — but the 14-day clock starts from your closed test, not from whenever your internal test began. Move today.

  1. Play Console → Testing → Closed testing. Create a track (the default is usually named "Alpha").
  2. Add your testers. An email list works; a Google Group is easier to manage at twelve or more, since people join without you editing a list each time.
  3. Upload your build and roll out. Expect review on first submission — budget a day or two.
  4. Copy the opt-in link and send it to your testers. Nobody counts until they accept it.
  5. Verify the opted-in count in Play Console before you start counting days. This is the step people skip, and it is why some tests quietly run at 9.

Keep the internal track. Using internal for fast iteration and closed for the requirement is a genuinely good setup, and the two do not interfere.

The part that is actually hard

Setting up the track takes twenty minutes. Finding 12 real humans who will install your app and leave it installed for a fortnight is the part that stalls launches for weeks.

That is the problem TestersWiz exists for: developers in the same position test each other's apps, every opt-in is verified against the developer's own Play Console list, and check-ins provide evidence the testing actually happened. Browse apps looking for testers, or read how it works for developers.

The honest caveat

Play Console's interface and Google's requirements both change. Verify against the official Play Console Help documentation before acting. Google alone decides production access, and TestersWiz is not affiliated with Google.

Next steps

Still need testers? Get 12 testers for your closed test through a free test-for-test exchange - you test another developer's app, they test yours, and every opt-in is verified.

Common questions

Does internal testing count toward the 12-tester requirement?
No. The requirement is specifically for a closed test. Internal testing is capped at 100 testers by email and is designed for your own team, not for satisfying production access.
What is the actual difference between the tracks?
Internal testing publishes almost instantly to a small list of named emails and skips full review. Closed testing goes through review, supports far more testers, and is the track Google's requirement refers to.
Can I run internal and closed testing at the same time?
Yes. Many developers keep an internal track for fast iteration and run the closed track for the requirement. They do not interfere with each other.

Apps currently in closed testing

Real developers running the test described above. Test one, and get testers for your own app back.

Closed testing

In Between is a free card game. Join the group, opt in, install, open it and play a hand. Keep it 14 days. Not available in South Korea. I test your app back the same day.

Games

Available in all countries

Open to testers · 14-day test

Closed testing

# BAYAA — Closed Testing: Instructions for Testers Thank you for participating in the BAYAA (بياع) closed testing program. BAYAA is a Mauritanian marketplace designed to connect customers with shops, restaurants, pharmacies, hotels, and service providers. ## 1. What testers are expected to do - Install BAYAA through the official Google Play closed-testing link. - Keep the app installed throughout the 14-day testing period. - Open and use the app regularly during the testing period. - Create an account and test registration and login. - Browse available shops, products, and services. - Test search and navigation. - Test merchant features if you have a merchant account. - Check WhatsApp contact options where available. - Report bugs, errors, confusing screens, and suggestions. ## 2. What feedback should you provide? Please tell us: - What worked correctly? - What did not work? - Were any pages slow or difficult to use? - Did you experience crashes or unexpected errors? - What features would you like us to improve? Honest feedback is very important. You do not need to give positive feedback if you encounter a problem. ## 3. Important testing rules - Use the app with your own tester account. - Do not share your login credentials. - Do not enter real payment or sensitive personal information. - Do not make fake purchases or transactions. - Do not uninstall the app during the testing period unless instructed. - Keep your Google Play testing enrollment active. ## 4. Reporting problems Send your feedback and screenshots of errors to the BAYAA development team. Thank you for helping us improve BAYAA and prepare it for its official launch in Mauritania. **BAYAA — بياع | Supporting Mauritanian Businesses**

Shopping

Available in all countries

Open to testers · 14-day test

Closed testing

PocketLedger helps you know your money and own your month — without handing your financial life to anyone. Everything stays on your phone. There is no account to create, no bank login, no SMS reading and no internet access at all. PocketLedger works fully offline. TRACK EVERY RUPEE (OR DOLLAR, EURO, POUND) • Add income and expenses in seconds, with category, account, date, merchant and notes • Mark refunds so they reduce your spending instead of counting as income • Search by merchant or note, filter by type, and tap any category to see its transactions for the month • INR, USD, EUR and GBP supported — amounts in different currencies are never mixed or converted SEE YOUR MONTH AT A GLANCE • Net cash flow, total income and total expenses for any month • Spending by category with an interactive chart • Recent transactions and account balances on one screen BUDGETS THAT KEEP YOU HONEST • Set a monthly limit for any category • See what you have spent, what is left, and when you go over ALL YOUR ACCOUNTS • Cash, bank accounts, UPI, credit cards and wallets • Pick from popular banks (SBI, HDFC, ICICI, Axis, Kotak and many more) and UPI apps, or type any name • Live balance for every account NOTHING IS EVER LOST • Every transaction keeps a full version history: see exactly what changed, when • Deleted transactions can be restored • An activity log records every add, edit, delete and setting change PRIVATE BY DESIGN • No sign-up, no ads, no tracking, no analytics • No internet permission — your data physically cannot leave the app • Not backed up to the cloud PocketLedger is a personal budgeting and expense-tracking tool. It does not offer loans, payments, banking or investment services and does not connect to any bank. Made by Technopreneurs Technolabs.

Finance

Available in all countries

Open to testers · 14-day test

May we use analytics and ad measurement? Analytics (Vercel, and Ahrefs on our public pages) count page views without cookies. Ad measurement lets Google's tag on our public pages see which visits came from our Google ads, using a Google cookie. The site works the same either way. Cookie Policy · How Google uses data ·