Can You Reuse Testers for Multiple Apps?
Each app needs its own closed test, but the same pool of testers can cover multiple apps. Here is how that works in practice.
The 12-tester requirement is per app, not per account. Every new package name needs its own closed test with its own 12 testers opted in for 14 days. You cannot carry testers over from one app to another, because the testing record must show that each app was tested independently.
What you can reuse is the pool. A service that maintains a standing roster of testers can assign the same pool to multiple apps, but each app gets its own 12 testers and its own 14-day window. The second app fills its roster faster than the first because the testers are already opted in to the platform, not because the requirement is lower.
If you are managing the recruitment yourself, the per-app rule means the second launch is as expensive as the first in calendar time. You have to find, brief, and retain a new set of 12 testers for each package. A managed service turns that into a dashboard action: add the app, pay for the plan, and the roster is assigned.
If this matches your situation
12Tests assigns 12 real Android testers within hours, runs the full 14-day window, and delivers a written report you can paste into Google's production access questionnaire. One-time payment per app, no subscription.