Guides & FAQ
From Google Play closed testing to production access — step by step with the TestDaş community.
Google requires 14 days of closed testing. Default target: 20 real testers — milestones day by day.
Day 0 · Start
Turn on closed testing in Play Console, add the [email protected] group, and submit your app on TestDaş. Testers join from the pool.
About 10 minutes
Days 1–14
20 real testers open the app every day and upload daily proof. You watch fill rate and feedback from My Dashboard.
Nothing required on your side
Day 14
Google’s closed testing period ends. Testers’ credits unlock; you’re ready to apply for production access.
Review status
Day 15+
Complete the form in Play Console, wait for approval, and create your production release. Most apps reach the store in about three weeks from first listing.
About 10 minutes + Google review
After approval, ship a production release. When Google finishes review, your app goes public on Play. Most apps reach live within about three weeks from first listing.
Four guides in order: setup through store listing.
Guide 1 · Day 0 · 6 min
From Play Console closed test setup to adding your app on TestDaş — listing rights, credits, and step-by-step settings.
Read guideGuide 2 · Days 0–14 · 4 min
From 20 testers joining to daily proof — day-by-day overview of fill rate, completion, and the closed test process.
Read guideGuide 3 · Day 15 · 5 min
When to submit the Play Console production access form and how to answer common questions.
Read guideGuide 4 · Day 17+ · 3 min
From the approval email to a production release and a public Play Store listing.
Read guidePlay test tracks and where TestDaş fits.
Background · 3 min
The invite-only closed testing stage new apps go through before the Play Store — in plain language.
Read guideBackground · 4 min
What each track is for and which one counts toward production access.
Read guideGood to know · 4 min
Common rejection reasons and how TestDaş helps you avoid them.
Read guideGood to know · 3 min
The 20-tester / closed test rule: second apps, personal vs organization accounts.
Read guideAbout · 5 min
Finding 20 testers through mutual help: credits, listing vouchers, and daily proof — overview.
Read guideRead only if it applies to your app.
Optional · Paid apps · 3 min
Paid-up-front apps: run a $0 / free price during the test period.
Read guideOptional · IAP · 3 min
Yes — with Google license test accounts and test cards; no real charges.
Read guideOptional · Country / language · 3 min
That’s fine. Widening country / language settings during the test is usually enough.
Read guideShort answers to common questions.
After your app is active in the pool and the first testers join. If the closed test track and Google Group are set up correctly, installs usually start the same day.
Yes. TestDaş is not a paid bot farm; members test each other’s apps. A daily screenshot is required.
Confirm [email protected] is on the closed test in Play Console, the release is live, and the package name matches your TestDaş listing. Still stuck? [email protected].
For new apps, typically enough real users in closed testing for at least 14 days. Thresholds vary by account type; follow the notice in your Play Console. TestDaş defaults to 20 × 14 days.
Most personal accounts need closed testing before first production launch. Apps already in production or organization accounts may differ — see the guide: “Does Google Play require 20 testers for every app?”
Yes. Complete 14 days on 3 different apps → 1 listing voucher. Repeatable (6 tests → 2nd voucher). Buying credit packs is optional.
Slots open when someone leaves early; new testers can join. Keep the closed test track and group active.
Not required. You can ship critical crash fixes; do not delete the track or tester list.
14 days closed testing + production access review (a few days) + production review. Most apps are on the store in about three weeks.
Yes — set price to free during testing or use license testing. See also: “Do testers have to buy the app?”
Yes, with Play license test accounts. No real charges. See: “Can testers try in-app purchases?”
Yes. Widen the country list in closed testing. See: “Is your app single-country or Turkish-only?”
Proof of testing confirms the app was actually opened, reduces download-and-delete abuse, and supports Google’s expectation of active closed testing.
Play Console → Test and release → Closed testing → Testers (email lists) → [email protected].
Email [email protected]. Replies are usually within a few hours.