How to Prepare Your App for Closed Testing
A complete closed testing release is more than a build number. Here is the checklist Google actually evaluates, and the order in which to complete it.
Before you recruit a single tester, the app needs to be in a state where a reviewer can install it, open it, and form an opinion. That means a live closed testing track in Play Console, a store listing that is complete, and a build that is the one you intend to ship.
The store listing is the part most developers underestimate. Google’s reviewers see the same listing a user sees, so placeholder screenshots, a missing privacy policy URL, or an incomplete content rating will block the review regardless of how good the testing record is. Complete the listing before you start the closed test, not after.
The build you test must be the build you ship. If you replace it mid-window with a new version, the opt-in streak for existing testers may reset, and the testing record becomes fragmented. Testing a build you are about to replace wastes the 14 days and can push the submission date back by weeks.
Finally, verify the opt-in link. Play Console generates a shareable URL for each closed track, and that URL is the handshake between your dashboard and Google’s testers. A link that points at the wrong track, a stale release, or an app that is not yet in closed testing will not accept anyone, and the days spent waiting for it to work are days lost from the window.
If this matches your situation
12Tests assigns 12 real Android testers within hours, runs the full 14-day window, and delivers a written report you can paste into Google's production access questionnaire. One-time payment per app, no subscription.