Show the real state
Empty campaigns look empty. A tester who has not opted in is not counted as a tester. Screens do not flatter the numbers, because a flattering number is a liability when you have to justify it.
About GetClosedTesting
Why this platform exists, the principles it is built on, and what we will and will not claim about Google Play.
Make closed testing evidence a by-product, not a project
Why this exists
Closed testing is a procedural requirement with a real cost. Someone has to recruit testers, collect their Google account addresses, confirm who actually opted in, watch whether they stayed active, and then account for the whole thing later.
In most teams that work lands on whoever is closest to the release, and it lands on top of their actual job. It gets tracked in a spreadsheet that is accurate on the day it is created and progressively less accurate after that.
GetClosedTesting exists to make that work a by-product of running the campaign properly. The roster, the participation record and the testing window are maintained because you are using the tool to run the test, not because someone remembered to update a sheet.
What we believe about the work
- Tracking is the product. A campaign workspace is only worth using if the state it shows is the state that is actually true.
- Opt-in and activity are different facts. Conflating them is how teams end up with a tester count they cannot stand behind.
- The record should be boring. If producing a campaign summary is exciting, the tracking failed somewhere earlier.
- Google decides, not us. Our job is to make what you did legible, not to imply we can influence the outcome.
Product principles
These are working rules rather than aspirations. They determine what gets built and what gets cut.
Your account stays yours
We never ask for access to your Play Console. You stay in control of the track, the release and the application, which also means you are never locked in to us to ship.
Roadmap is labelled as roadmap
Features that are not finished are marked upcoming. Nothing is described as available because it is planned.
No guarantees we cannot back
No guaranteed approval, no guaranteed production access, no invented success rates. Where we describe Google's policy we say so, and we tell you to check the current requirements yourself.
Built for the second release
A tester pool that has to be rebuilt every release is a cost you pay repeatedly. Rosters and campaign history are designed to carry forward.
Prefer boring reliability
The testing window is a hard deadline. A tool that is occasionally unavailable during it is worse than a spreadsheet, so reliability outranks novelty.
What we commit to, and what we will not claim
Transparent testing
Every campaign record is visible to the team that owns it, including the parts that look bad. If tester participation dipped in the middle of a window, that is in the record, because a record that only contains good news is not evidence of anything.
Where a claim about Google Play appears on this site, it reflects the policy as published at the time of writing. Google changes requirements without notice, so each policy page carries a last-reviewed date and links to the official documentation.
What we will not do
- We will not claim that using this service guarantees production access or approval.
- We will not publish testimonials, ratings or success statistics that we cannot substantiate.
- We will not simulate testers, inflate opt-in counts or generate synthetic participation.
- We will not ask for credentials to your Google Play account.
Talk to us
Questions, corrections or requests go to [email protected]. We would rather be told something on this site is out of date than leave it standing.
Start With a Campaign
If the approach here matches how you want to run testing, the next step is a campaign. Tell us about the app and we will confirm scope before anything begins.