Do you need 12 new testers for every app you publish?

Updated

Every new app needs its own closed test, but not necessarily new testers. If your personal developer account was created after 13 November 2023, each app you publish goes through its own fourteen days with at least twelve opted-in testers. The people can be the same ones who tested your last app.

Is the requirement per app or per account?

Per app. Google's page says personal developer accounts created after 13 November 2023 must "test their apps before those apps are eligible for distribution on Google Play." Production access is granted to an app, after that app's own test.

So passing the test once does not unlock production for everything you publish later. Your second app starts at day zero, with its own closed track.

Can I use the same testers again?

Nothing in Google's requirement says testers have to be new. What matters is that they are real people, opted in to this app's closed test, for the preceding fourteen days.

In practice that means each tester has to:

  1. Join the new app's test. Every app has its own closed track and its own opt-in link. Being opted in to your first app does nothing for the second.
  2. Stay opted in for the new window. The count starts from their opt-in to the new app, not from when they joined your first test.

This is also where reuse saves time. Google's email lists can be reused across your apps, and a Google Group is just an address you can add to the new app's track as well, so a group of testers who are happy to help again can be added in minutes. They still have to open the new opt-in link and accept.

Does reusing testers hurt my application?

Google does not publish anything against it. What the production access application does ask about is the test itself: how you recruited testers, how engaged they were, and what feedback they gave on this app. Testers who actually use the new app and tell you something useful about it give you better answers than a larger group that opts in and forgets.

If your new app is for a different audience, some new testers who are that audience are worth recruiting for the feedback alone.

What about updates to an app already in production?

The requirement is about making an app eligible for production. Google's page does not describe repeating the test for updates, and once an app has production access you release updates to it through Play Console as usual.

Is there a way around testing every app?

The requirement applies to personal accounts created after 13 November 2023. Organisation accounts, which need a D-U-N-S number and a registered organisation, are not subject to it. For a solo developer that is a bigger step than running the test, but if you are a registered business publishing several apps, it is worth knowing.

Otherwise, plan for it: keep your tester group, keep in touch with them, and find a few more for free when you start the next app.

Sources

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 every new app need its own closed test?
Yes, for personal developer accounts created after 13 November 2023. Google's wording is that these accounts must test their apps before those apps are eligible for distribution, so each app runs its own test.
Can the same 12 testers test my second app?
Nothing in Google's requirement stops it. Each tester opts in to the new app's closed track with its own opt-in link, and the new app's 14 days start from those opt-ins.
Do app updates need another closed test?
Google's requirement describes testing an app before it is eligible for production; it does not describe repeating it for updates. Once an app has production access, you release updates as normal.

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

Related guides

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 ·