Yes—tester exchange between real developers is allowed when everyone genuinely opts in, installs, and uses the apps. Google prohibits fake engagement, bots, and review manipulation—not mutual help. Personal accounts after November 13, 2023 still need ≥12 opted-in testers for 14 consecutive continuous days; org/D-U-N-S accounts are exempt. Opt-in without real use remains a rejection risk.
What Google Cares About
Play cares about authentic testing that improves app quality and demonstrates legitimate pre-launch use.
Real testing
- Real people on real devices
- Actual installs and sessions during the closed test
- Opportunity to find bugs before production
- Continuous participation across the required window
What they prohibit
- Fake accounts, bots, or fabricated engagement
- Self-testing schemes meant to game metrics
- Paid or coordinated review/rating manipulation
- Fraudulent patterns that misrepresent user behavior
Tester Exchange Reality
A healthy exchange is peer QA with mutual incentives—not a loophole around policy.
What it is
- Developers opting into each other’s closed tests
- Downloading and using apps across consecutive days
- Reporting crashes and blockers
- Helping peers meet the official 12-tester / 14-continuous-day bar (previously 20)
What it is not
- Automatic “install bots”
- Empty email lists with no opens
- Trading five-star reviews
- Artificial retention scripts
Why Community Testing Is Fine
Community testing aligns with the policy intent when behavior stays genuine.
It is real testing
- Human testers, real devices, real sessions
- Bugs can surface and get fixed
- Engagement can be inspected in Play Console
It meets intent
- Apps improve before public traffic
- New personal accounts demonstrate readiness
- Requirements are met without fabricating users
No policy violation by default
- Mutual testing ≠ review exchange
- Helping peers ≠ rating fraud
- Organic communities can stay compliant when rules ban fakes
The Key Distinctions
Stay on the allowed side by separating testing help from store-signal manipulation.
Allowed
- Opting in and using each other’s closed-test builds
- Sharing setup tips for Release → Testing → Closed testing
- Reminding peers to open apps daily
- Collecting bug reports privately
Not allowed
- Coordinating Play Store reviews or star ratings as payment
- Fake devices or automated engagement farms
- Misrepresenting tester identity or activity
- Any pattern designed to deceive Play’s systems
Closed Test Pro Approach
Closed Test Pro facilitates organic developer-to-developer closed testing with tracking aimed at real 14-day participation—not fabricated metrics. Use exchanges to produce genuine engagement Google can trust when you apply for production.