Google Play ১২ টেস্টার / ১৪ দিন: সম্পূর্ণ গাইড

কাদের করতে হবে, কীভাবে ক্লোজড টেস্টিং সেট করবেন এবং প্রথমবারেই প্রোডাকশন অ্যাক্সেস পাবেন।

If you opened a personal Google Play developer account recently, the Production page in Play Console stays locked until you finish one requirement: a closed test with at least 12 testers who stay opted in for 14 consecutive days. This guide explains the rule in plain words and shows the fastest way to pass it.

What is the 12 testers / 14 days rule?

Google requires new personal developer accounts to prove that real people have used the app before it reaches the public store. Until a closed test clears both numbers, only your testers can install the app and the button to apply for production access stays disabled.

When the policy launched in late 2023 the minimum was 20 testers. Since December 2024 it has been 12 testers, while the 14-day window stayed the same.

Who must do it?

• Personal developer accounts created after November 13, 2023.
• Organization (company) accounts with a verified D-U-N-S number are not subject to this testing requirement.
• Every new app on an affected personal account needs its own closed test.

Set up closed testing in Play Console, step by step

1. Create the app and complete the store listing, content rating, data safety, target audience and ads declarations.
2. Open Testing → Closed testing and create a track (or use the default Alpha track).
3. Upload a signed Android App Bundle (.aab) and roll out the release.
4. Under Testers, add an email list or a Google Group. Using a Google Group makes it easy to add our testers in one step.
5. Select countries/regions and send the release for review. Small changes are usually reviewed within hours to a few days.
6. Copy the opt-in link (Join on the web) and share it with your testers. Each tester must opt in and install the app from Google Play.

How the 14 days are counted

Play Console counts testers who are opted in to your closed test. You need at least 12 of them, continuously, for 14 days. If testers leave or never install, the progress may not complete, which is why we always assign 15 testers instead of the bare minimum.

Daily, genuine usage matters: Google later asks how testers engaged with the app and what you changed based on their feedback.

Applying for production access

When the checklist shows the requirement as met, open Dashboard → Apply for production. You answer questions about your closed test (how you recruited testers, how engaged they were, what feedback you received), about the app (purpose, audience) and about production readiness (what you changed). Specific, honest answers are approved much more often than vague ones. Google usually replies within a few days.

Common reasons for rejection

• Testers opted in but did not actually use the app.
• Fewer than 12 testers stayed opted in for the full 14 days.
• No app updates were published during testing, so there is no evidence feedback was used.
• Vague answers in the production access questionnaire.

Tips to pass on the first try

• Use 15 or more testers so drop-outs never break the count.
• Ship at least one update during the 14 days that fixes issues testers reported.
• Keep notes of feedback and reference them in your answers.
• Make sure core features work without a login wall, or provide test credentials.

Let us handle the testing

With 12TestersPro you get 15 real testers on real Android devices who join within hours and use your app every day for 14+ days, plus a feedback report and help with the production questionnaire. Pay with PayPal, MoMo or VNPay.