16
Developers per flock
Built for Google Play closed testing
Find 12 testers for your 14-day closed test
TestFlock connects indie developers with other indie developers who all need to clear Google Play's closed testing requirements — no cold outreach, no one-sided testers who disappear.
Join the community
16
Day test runs
1:1
Extra test partners
30s
Daily usage verified
How it works
A simple path from closed testing to production access.
1
Join the Google Group
Join the TestFlock Google Group with your account to access closed testing tracks.
2
List your app
Add your Play closed-testing app, share test instructions, and paste your opt-in link. See the Play Store setup guide.
3
Join a Flock
Join a 16-member flock so everyone tests everyone else’s app for 16 days.
6
Share feedback
Leave constructive feedback. Plain eggs reward activeness; golden eggs reward helpful reviews.
5
Check in daily
Open each mate’s app for at least 30 seconds a day. Usage is verified automatically.
4
Add FlyMates
Find 1:1 testing partners outside your flock for extra coverage when you need it.
Why TestFlock
Built for structured closed testing
TestFlock gives indie Android developers the structure, accountability, and feedback they need to complete Google Play closed testing with confidence.
Google Play requires at least 12 testers for 14 consecutive days. TestFlock makes that doable.
Structured flocks of 16 developers
Balanced groups where developers test one another’s apps and progress together.
FlyMates for extra coverage
Add 1:1 testing partners when you need more installs, usage, or feedback.
Daily usage verification
Automatic checks confirm assigned apps were genuinely opened and used.
Incentivised feedback system
A reputation-based system encourages useful feedback instead of empty check-ins.
Reputation system
Reputation built on consistency and helpful feedback
TestFlock uses two reputation signals to highlight FlyMates who are active, consistent, and provide helpful feedback — so you can choose with confidence.
Plain eggs — daily check-ins
Earned by consistently completing daily check-ins and showing up during testing. This helps identify active, dependable testers.
-
Daily check-ins Open assigned apps for at least 30 seconds each day
-
Consistency signal Higher counts show who reliably shows up throughout the run
-
Active FlyMates Sort by Most active to find dependable testing partners
Golden eggs — helpful feedback
Earned by submitting helpful feedback that drives improvements. This helps identify testers who provide useful, actionable insights.
-
Constructive feedback Leave useful notes after check-ins, not empty comments
-
Peer-rated quality Earn eggs when feedback is marked helpful or very helpful
-
Helpful FlyMates Sort by Most helpful when you want actionable insights
Guides
See our guides
Tips, comparisons, and walkthroughs for Google Play closed testing.
Google Play production access questions and sample answers
See the questions Google Play asks when applying for production access, with real sample answers from an indie Android developer’s closed testing application.
Best Platforms to Find 12 Testers for Google Play Closed Testing
Compare Testers Community, App Hive, TheClosedTest, SwapTest, BetaCircle and TestFlock for Google Play’s 12-testers-for-14-days rule.
Google Play production access rejected? Here's how to fix it and get approved
Common rejection reasons, how to fix closed testing gaps, and a checklist before you apply for production again.
TestFlock vs Testers Community: which Android beta testing app is right for you?
Android usage stats, 30-second auto-verification, pack dropouts, FlyMates, usage statistics, and passing the 12 testers for 14 days requirement.
How to get 12 Android testers for 14 days on Google Play
Everything you need to know about Google Play's personal app testing requirement and how to pass it.
Google Play closed testing: a developer's guide
Complete guide to Google Play closed testing for personal developer accounts — tester requirements, opt-in links, and how to move to production.
FAQs
Frequently asked questions
Quick answers about closed testing, the 12 testers for 14 days rule, and TestFlock.
Developers with affected personal Google Play developer accounts must run a closed test with at least 12 testers continuously opted in for a minimum of 14 days. Completing the period lets you apply for production access, but does not automatically guarantee approval.
The current minimum is 12 testers continuously opted in for at least 14 days. Older guides sometimes mention 20 because Google previously used a higher threshold — follow what Play Console shows for your account.
Google does not publish a rule requiring every tester to open the app every calendar day. Still, Google asks about tester engagement for production access, so testers should use the app regularly and provide real feedback — not only opt in once.
No. Meeting the numerical requirement makes you eligible to apply, but Google still reviews testing quality and your application answers. Weak engagement, vague answers, or unresolved issues can lead to rejection.
Ready to pass Google Play closed testing?
Join TestFlock, list your app, and find your flock today. Free for developers and testers.
