PlayTestersby Alpha MF

Guide 6 of 7 · Updated October 2026

Closed testing checklist: 14 days, step by step

Short answer: Before day 0, set up the closed track, the tester list, the store listing and App content, and screenshot the dashboard the day your 12th tester opts in. Days 1–3 are for installs and first feedback, days 4–7 for an update to the track, days 8–12 for a second feedback round. Draft the application on day 13 and apply on day 14, keeping the tester count at 12 or more every single day.

The closed test Google requires from new personal developer accounts has a fixed shape: 12 testers, 14 continuous days, then an application. What you do inside those 14 days decides whether the application is approved. This is the whole thing as a checklist — print it or tick it off in your head — with the calculator turning it into dates.

Last updated: · About 7 minutes · Background: the 12-testers rule explained.

Before day 0: setup

  • Developer account verified. Identity verification done; the account's "Verify" tasks on the Play Console home page are all complete.
  • App created and App content started. Privacy policy URL, data safety form, content rating, target audience, ads declaration — at least begun, ideally complete. Google reviews these at the production access stage too.
  • Closed-testing release uploaded and rolled out. Test and release → Testing → Closed testing → the track (Alpha) → create release → upload the bundle → review and roll out. The first release goes through app review; allow a few days.
  • Countries selected on the closed track. Add every country your testers might be in.
  • A tester list attached. An email list, a Google Group, or both. Which one when.
  • Opt-in link copied from the Testers tab: https://play.google.com/apps/testing/your.package. Where it is.
  • Feedback channel. A three-question form (what did you try, what was confusing, what would you change) or a plain "reply to this message".
  • Tester brief written. Two lines on what the app does and one specific thing to try. Template.
  • Testers lined up. Aim for 14–15 so one dropout does not reset your clock. Every free way, plus the paid shortcut.

Day 0: twelve opted in

  • Send the opt-in link with the brief, one-to-one where you can.
  • Watch the dashboard's closed-testing card. When it shows 12 testers, take a screenshot with the date visible.
  • Write the date down: this is day 0. Put it in the 14-day calculator to get the earliest application date and reminders.
  • Ask every tester to confirm they installed and opened the app. Opt-in is what the counter measures; installs are what your answers will rest on.

Days 1–3: installs and first feedback

  • Check the tester count once a day. If it dips, replace the tester the same day.
  • Compare installs on the closed track (Statistics, filtered to the track) with opt-ins. Nudge anyone who has not installed.
  • Open Testing → Pre-launch report. Fix every crash and ANR it found; note them in a log.
  • Send the first feedback request on day 2 or 3. Log every reply: date, tester's initials, what they said.

Days 4–7: the first update

  • Release an update to the closed track (a new version code) with release notes that name the feedback: "Fixed the crash when rotating the map screen (reported by two testers)."
  • Tell testers an update is out and ask them to try the thing that changed.
  • Day 7: midpoint. Count still 12 or more? Installs close to 12? Feedback from at least three people? If any of these is no, act now — the second week is short.

Days 8–12: second round

  • Second feedback request, this time about the update and anything still confusing.
  • Second update if there is something worth shipping. Two updates in 14 days is a very normal test; zero is the problem.
  • Keep logging. The log is the application — by day 12 it should hold at least five concrete feedback items and the versions that answered them.
  • Finish every App content item in Play Console. Check the store listing says what the app actually does.

Day 13: draft the application

  • Draft the answers in a document, from the log: how many installed, how many used it more than once, what they said, what changed in which version. The questions, with sample answers.
  • Take a fresh screenshot of the tester count and the track's release history for your own records.
  • Ask testers to stay opted in until you tell them you have production access.

Day 14–15: apply

  • Open the app's dashboard. If the requirement card has become Apply for production access, apply with the drafted answers.
  • If the count is 12 but the button has not appeared, a tester's 14 days are not complete yet (someone was replaced). Wait; do not create a new track or a new app. The calculator shows the effect of a replacement.

While Google reviews, and after

  • Review takes up to 7 days; one to three is common. Keep the test running and the testers opted in meanwhile.
  • Approved: create the production release (it goes through app review like any release), thank the testers, and ask them to stay a few more days until it is live.
  • Not approved: read the six reasons and fixes, keep the test running, and apply again after a further 14 days — the second application is usually the one that passes.

One rule for all 14 days: never let the count fall below 12. With exactly 12 testers you are one uninstall-and-leave away from waiting again; with 14 you are not.