No. If the testing requirement applies to your account, you can't skip it, shorten it or replace it with something else. A personal developer account created after November 13, 2023 must run a closed test with at least 12 testers opted in continuously for at least 14 days before it can apply for production access. What you can do is make sure the test runs once, cleanly, without lost days.
First: does the rule apply to you?
Google's official wording covers personal accounts: "Google Play requires personal developer accounts created after November 13, 2023, to test their apps before those apps are eligible for distribution on Google Play" (App testing requirements).
Google's help article doesn't mention organization accounts. Community Product Experts describe organization accounts, and personal accounts created on or before November 13, 2023, as unaffected. That's likely accurate, but it isn't Google's own wording, so check what your Play Console shows. If your Dashboard asks you to complete testing before applying for production, the rule applies to you.
Personal vs organization developer accounts explains the two account types in more detail.
What is locked until you finish
For accounts under the rule, Google says that "certain features in Play Console, such as Production … and Pre-registration …, remain disabled until developers meet these testing requirements." Open testing "becomes available after you gain production access."
So there's no public track available to you until you've completed the closed test and been approved. The order is fixed: closed test, apply, then production.
Things that don't count as skipping
Developers often look for a shortcut. These are the ones that come up most, and why they don't work:
Internal testing instead of closed testing
Internal testing is faster to set up and builds are "normally available to testers within seconds". But Google states that only a closed test meets the requirement. Internal testers don't count, no matter how many you add. See internal vs closed vs open testing.
Fewer testers or fewer days
The numbers are minimums. Eleven testers, or 12 testers for 13 days, doesn't meet the rule. Google lists having "fewer than 12 opted-in testers" as a reason to require more testing. The count is measured when you apply: at least 12 testers must be opted in at that moment, each for the preceding 14 continuous days.
Testers who opt in and leave
"Testers who opt in, test for fewer than 14 days, and then opt out do not count toward the requirement." If someone opts out and back in, their 14 days must be consecutive. What counts as an opted-in tester covers the details.
Fake testers
Emulators, bots, or a set of extra Google accounts you control don't give you real testers. The requirement is about real people using your app, and Google's policy says "techniques to evade app reviews are not allowed." That's a risk to your account that isn't worth taking.
Someone else's account
Publishing under another person's older account to avoid the rule means your app lives in an account you don't control, under their name and identity verification. We don't recommend it. If you are genuinely an organization, an organization account is a legitimate choice, but it requires a D-U-N-S number and organization verification, and you should choose it because it describes you, not as a workaround.
Why there's no shortcut
Google introduced the rule so that apps from new accounts are tested by real people before launch. Its stated aim is to let developers "test their app, identify issues, get feedback, and ensure that everything is ready before they launch." A shortcut would defeat the point. If you're curious about the background, read why Google requires closed testing.
How to lose as little time as possible
You can't skip the 14 days, but you can avoid adding to them. The delays that hurt most come before and after the test, not during it.
- Finish account verification early. Identity and device verification can take time. See developer account verification problems.
- Complete app setup before you upload. Closed testing requires it, including App content declarations and the Data safety form.
- Send everything for review together. Track, testers, countries and release go to Publishing overview in one batch. Closed track reviews can take a few hours or up to seven days, longer in exceptional cases.
- Have more than 12 testers. A small buffer protects you if someone drops out.
- Keep testers active. Google may require more testing for "insufficient tester engagement".
- Apply soon after day 14. Don't let testers leave before you submit. How to apply for production access walks through the form.
After you apply, Google says review "usually takes seven days or less, but can occasionally take longer." If more testing is required, you may need to keep the closed test running and reapply when ready.
Key takeaways
- If the rule applies to your account, there's no way to skip it.
- Internal testing, fewer testers, fewer days or fake testers don't meet the requirement.
- Nothing shortens the 14 days; good preparation prevents extra days.
- Google makes the final decision on production access.
GoPlayTester can't skip or shorten the test either. What we do is supply 12+ real testers on real devices for the full 14 days, with a step-by-step setup guide, so the test runs cleanly the first time. You can order here.
