If your personal Google Play developer account was created after 13 November 2023, you cannot publish straight away. Google requires a closed test first: at least 12 testers, opted in continuously for 14 days. After that you apply for production access, and you answer questions about your test, your app, and how ready it is.

This guide walks through those questions, one by one, and shows how to answer each with the records you should be keeping during the test. It is based on Google's own help page. Google can change the form, so check that page before you apply.

Before you apply: keep these records

Google says you must summarize your testing feedback when you apply, and it advises you to keep a record of the feedback you receive. Start a simple table on day one:

Date	Who tested	What they tried	What they found	How serious	What you changed	Fixed?

Ten minutes a week is enough. Without it, you will be inventing your answers from memory on application day.

Part 1: About your closed test

This part checks that the app was tested properly before it reaches users. There are three questions.

1. How easy was it to recruit testers? You pick an option. Be honest: nothing is gained by claiming it was easy if it was not.

2. Tester engagement. Google asks:

• Did your testers use all the available features of the app?
• Did their usage match how real users are expected to behave? If not, what was different?

What a good answer needs: specific features, not "everything worked". For example, name the areas that were tested and the areas that nobody reached.

Example (a fictional note-taking app): "Testers used the editor, folders, search and sync every day. Nobody tested the export feature, because it needs a paid account. Real users will probably create more notes than our testers did, so we expect search to be used more in production."

3. Summarize the feedback and how you collected it. Describe what testers told you and through which channel (a form, email, a group chat, Play Console's testing feedback page).

Example: "We collected feedback through daily check-ins with a screenshot and a written note, and through the Play Console testing feedback page. The three main themes were: a button hidden behind the navigation bar on some phones, search ignoring accented letters, and low contrast in dark mode."

Your feedback table from the step above is exactly where this answer comes from.

Part 2: About your app or game

Google says these answers are not shown publicly and do not affect your app's visibility, your access to Play Console features, or your eligibility for developer programs. Still, answer them properly.

• Target audience. Be as specific as you can. "Everyone" is not an answer. "Students preparing for exams who study on their phones" is.
• Value proposition. For an app: how does it help users? For a game: what makes it different?
• Estimated installs in the first year. Pick the range you honestly expect.

Part 3: About your production readiness

Two questions, and they are the ones people write worst:

1. What did you change because of what you learned in the test? List real changes. If you fixed nothing, say what you reviewed and why you decided nothing needed to change.

Example: "We moved the Save button above the navigation bar, made search ignore accents, and raised the contrast of hint text in dark mode. We re-checked all three on two different phones."

2. How did you decide the app was ready? Say what you checked: the issues that were fixed, the ones you accepted and why, and your stability check (crashes, broken screens).

What happens after you apply

Google reviews your application. It says the review usually takes seven days or less, and sometimes longer. You get an email when it is finished.

If Google asks you to keep testing, two reasons it names are fewer than 12 opted-in testers and insufficient tester engagement during the test.

Five mistakes to avoid

1. Counting testers who left early. Testers who opt in, test for fewer than 14 days and then opt out do not count. If someone opts out and back in, the 14 days must be consecutive.
2. Treating "12 testers" as the whole job. Google also looks at engagement, not just the number.
3. Writing vague answers such as "testing went well".
4. Copying someone else's answers. Yours should describe your app and your test.
5. Skipping the policy check. Google says review is not a troubleshooting step: apps that break policy or crash get rejected.

Where ClosedTest fits

If you want help with the testing itself, ClosedTest runs closed tests with real Android testers and gives you the records Google asks about: daily check-ins with screenshots, written findings, device coverage and a final report. You can see the format in our sample report (a fictional app, real layout).

We cannot guarantee that Google will approve your app. Google makes that decision. What we can give you is honest evidence of what was tested, which is what the form asks for.

ClosedTest is an independent service and is not affiliated with Google.