A window you can state exactly
Start date, end date and the number of continuous days, recorded as the campaign ran rather than reconstructed afterwards.
How GetClosedTesting Works
The full journey, from campaign setup to the testing evidence you keep afterwards: what your team does, what we handle, and where the boundaries are.
What the process actually involves
Closed testing has a fixed shape. What varies between teams is how much of the coordination work they have to hold in their heads.
What stays with you, and what we take on
Your Google Play account stays yours. You create the closed testing track, manage the release, and submit the production access application. None of that changes, and we never ask for access to your Play Console.
What we take on is everything around it: keeping the tester roster accurate, knowing which testers have opted in and which have gone quiet, tracking days elapsed against the window you committed to, and holding the feedback in a form you can actually use later.
How long it takes
Setup is measured in hours, not weeks. The part that dominates the calendar is the testing window you commit to, which is set by Google's current requirements for your account type rather than by us.
- Campaign setup and roster preparation: typically one working session
- Tester invitations and opt-ins: a few days, depending on how quickly your testers respond
- The testing window itself: the continuous period you have committed to
- Feedback consolidation and summary: an afternoon at the end of the window
Because Google's requirements change, confirm the current minimum tester count and continuous-day requirement in the official Play Console documentation before you commit to a date.
Who does what
- You: create the track, upload the build, invite from the roster we maintain, decide when to apply for production access
- Testers: opt in with the Google account they were invited with, install the build, report what they find
- GetClosedTesting: maintain the roster, monitor participation, track the window, hold the feedback record, prepare the campaign summary
Setting the track up in the Play Console
This part stays with you. Five screens in the Play Console, in the order you reach them. These are the real console screens, not illustrations.
1. Open Test and release, then Closed testing under Testing. Every closed test starts here. 
2. Create or manage the track that the testers will be added to. 
3. Paste tester addresses here. This is the list we keep accurate for you, and the one that decides your real tester count. 
4. Choose where the test is available. A tester outside this list cannot opt in, however many times they try. 
5. Roll the build out to the track. Testers then install from the opt-in link on their own device.
Four stages from setup to evidence
Each stage has a defined output. Nothing moves forward until the previous stage is actually complete.
Campaign setup
Record the app, the build under test, the track you will use and the testing window you are committing to. The campaign is created with the dates already fixed.
Tester coordination
Build the roster from the addresses you have, import existing spreadsheets, and track who has accepted the invite and with which Google account.
Testing window
Participation is monitored continuously. Opt-in status, activity and days elapsed are visible together, so a tester who has gone quiet is spotted while there is still time to replace them.
Feedback and reporting
Findings are logged against the build they came from. At the end of the window the campaign summary records what was tested, for how long and by how many active testers.
Two numbers decide the campaign
Everything else is detail. If these two are right for the whole window, the rest is bookkeeping.
Days at or above the tester threshold, and days elapsed
A campaign is healthy when the opted-in tester count stays at or above the threshold you need, continuously, for at least as long as the window requires. Both halves matter. A count that dips in the middle is a different problem from a count that never reached the threshold, and they need different responses.
- Opted-in testers on each day of the window, recorded as it ran rather than reconstructed
- Days elapsed against the window, so you know how much margin remains
- Any day the count fell short, kept in the record rather than smoothed over
- The date each tester opted in, which is what makes a continuous period provable
Preparing the application
Production access is granted by Google. What you control is how clear and accurate your testing record is when you apply.
Participation you can evidence
How many testers opted in and how many remained active, tracked separately so you are not overstating the count.
Feedback you can summarise
Findings grouped by build and device, so describing what testing surfaced is a matter of reading rather than remembering.
Consistency with what you submit
The record exists before the form is filled in, which makes it far easier to describe the testing accurately.
Questions about the process
The process questions we are asked most often during onboarding.
Ready to Set Up Your Campaign?
Tell us about the app and the testing window you are working towards. We will confirm scope, tester requirements and what happens next before anything starts.
Setup usually takes a single working session once the tester list is available.