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.

Applying for production soon? Check your APK against the Google Play launch checklist - target API, permissions that need a declaration, your Data Safety form and leaked keys. The first check is free.

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

Testers must join the Google Group using the same Google account they use on their Android device's Google Play Store. Testers must open the opt-in link, tap Become a tester, and then download the build via the Play Store link provided.

News & Books

Open to testers · 14-day test

Closed testing

Hi! I’m looking for testers for Crew Bites, a Flutter app that helps groups organize food orders, track who ordered what, and calculate the final bill fairly. Please test the main flow: add people, add food orders, select a restaurant/bundle, add tax/service/tip/delivery, review the total, and save or share the result. I’d especially appreciate feedback about usability, layout, performance, and any bugs on your Android device. Thank you!

Food & Drink

Open to testers · 14-day test

Desert Warrior: Last Battle is a 2D run-and-gun shooter. Please test the controls, 360-degree shooting, weapons, enemies, levels, coins and overall gameplay. Please play regularly during the 14-day test and report any crashes, bugs or issues you find.

Games

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 ·