The parts of closed testing that are really bookkeeping problems, kept in one place so the state of a campaign is something you read rather than reconstruct.
Everything here is live. Nothing is described as available because it is planned.
Keep a single, current roster of everyone testing your app.
Store tester email addresses, track who has accepted the invite, and see which Google account each tester opted in with. Rosters stay reusable across campaigns so you are not rebuilding the list every release.
Every campaign has a start date, a target and a current state.
Record the track you are using, the build under test and the dates you committed to. The campaign view keeps the current state of the test explicit instead of buried in a spreadsheet.
See how far through the testing window you are.
The dashboard summarises days elapsed against days required, tester counts and outstanding actions so you can tell at a glance whether the campaign is on schedule.
Distinguish invited, opted in, active and inactive testers.
An invite is not the same as participation. Trackers record opt-in status and last activity per tester so you can replace a tester who never installed the build before it costs you the window.
Collect findings in a structured, per-campaign record.
Testers and your team log issues against the build under test with steps to reproduce, device details and severity. Feedback stays attached to the campaign it came from.
A durable record of every test you have run.
Past campaigns keep their dates, tester lists and outcomes, so you can answer questions about a previous release without reconstructing anything from memory.
On the roadmap, not in the product. Listed so you know what is coming rather than discovering it is missing.
Reminders before a tester goes quiet.
Planned: scheduled reminders to testers approaching an inactivity threshold, and internal alerts when a campaign milestone is at risk.
Exportable campaign summaries.
Planned: a printable campaign summary covering the testing window, tester participation and feedback collected, ready to keep with your release records.
The individual views matter less than the fact that all of them read from one record.
How the workspace behaves, and where its edges are.
Tell us about the app and the testing window. Scope, tester numbers and cost are confirmed in writing before anything starts.