Guide · Google Play

How to pass closed testing first time.

Twelve testers for 14 days gets you to the application. The application is where people get sent back. Here's how to run the test so the answers write themselves.

7 minute readUpdated 18 November 2026

In short

  • Before day one: a stable build, a reviewed closed track, an accurate listing and a test login if your app needs one.
  • Choose testers who will open the app more than once, and ask them for specific feedback.
  • Ship at least one update during the test, based on what testers found, and write down what you changed.
  • Answer the application with specifics: numbers, examples and changes. Vague answers are the most common way to be asked to test again.

01Get ready before day one

Google is clear that review isn't a troubleshooting step. Sort these out before testers arrive:

  • The app opens and works on a few real Android phones, with no crashes or missing screens.
  • Your store listing, target audience and content rating are accurate.
  • If the app needs a login, you have working test credentials ready for Google.
  • The closed testing release has been reviewed, so the opt-in link works.
  • You know how testers will send feedback: a short form, email, or a group chat.

02Choose testers who will actually use it

Google asks about engagement, so the best testers are people who will open your app a few times over the two weeks, not once on day one.

Give them a reason to come back. Ask them to try one feature on day one, another a few days later, and to tell you what confused them. A short message every few days helps more than one long brief at the start.

And recruit more than 12. Sixteen gives you room for the person who swaps phones or leaves by mistake.

03Keep notes as you go

When you apply, you'll summarise the feedback and how you collected it. That's easy if you kept a simple log from day one:

DateTesterFeedbackWhat you did
Day 3Tester 4Couldn't find how to delete an entryAdded a delete option to the entry screen
Day 6Tester 9Reminder came at the wrong timeFixed time zone bug in version 1.0.3

A spreadsheet is plenty. What matters is dates, real quotes and what you changed.

04Ship an update during the test

One of the questions asks what you changed because of testing. The strongest answer is a real update you shipped to the closed track while the test was running.

Uploading a new version to the same closed track doesn't opt anyone out, so it doesn't touch your testers' 14 days. Fix two or three things testers raised, release it, and tell testers to update.

05Answer the application properly

Short, vague answers are the easiest way to be told to keep testing. Compare these:

WeakStrong
Testers liked the app.16 testers used the app over 14 days. Most opened it several times a week. Their main complaints were the reminder timing and finding the delete option.
We fixed some bugs.We released version 1.0.3 on day 7, fixing a time zone bug in reminders and adding delete to the entry screen, both raised by testers.
It's ready.No crashes reported in the last 7 days of testing, all core flows tested on Android 12 to 15, and every tester issue marked high priority is fixed.

06If you're asked to keep testing

It isn't the end. Read Google's message carefully: it usually points at too few testers or too little engagement. Keep your testers opted in, give them something new to try, collect another round of feedback, and apply again with better answers.

Want the testing part handled?

16 real testers who use your app for 14 days, with their notes and a summary you can use in your answers.

Keep reading

Related guides.

Get started

See your app through a stranger's eyes.

Your first test is free: three matched testers and a short fix list. No card.

Rather be on the other side? Become a tester