What you actually receive after the 14 days
Most testing services promise "detailed reports" and show you nothing until you have paid. Here is the exact structure of a TesterBee campaign report, section by section, so you can judge it before you order.
Senior full stack developer specializing in Laravel, React, and Firebase. Helped 1,200+ Android developers pass Google Play Closed Testing and publish apps. Expert in Play Console, production access, and Android app publishing.
The short answer
Every TesterBee campaign ends with one written report split into four parts: a device and engagement summary of your 14-day window, reproducible bug reports ranked by severity and priority, consolidated usability feedback, and draft answers for Google’s production access questionnaire. The format is identical at every tier. A higher tester count increases the volume of feedback, not the depth of the report.
The four sections of every report
Device and engagement summary
Which devices and Android versions your testers used, how many days each tester was active, and where the count stood on each of the 14 days. This is the section you screenshot if Google ever questions whether your testers were real.
- Device model and Android version per tester
- Active days out of 14, per tester
- Daily opted-in count across the window
- Any replacement events and their dates
Bug reports
Each bug is written so you can reproduce it, not just read about it. Severity and priority are ranked separately, because a cosmetic issue on a niche device is not the same as a crash on launch.
- Severity and priority, ranked independently
- Step-by-step reproduction path
- Expected result vs actual result
- Device, Android version, and app build number
Usability feedback
Where testers got confused, what they expected to happen, and what they gave up on. This is the part that changes your app rather than your bug tracker.
- Screen-by-screen friction notes
- Onboarding and first-run observations
- Feature discoverability issues
- Consolidated themes across testers, not one-off opinions
Production access questionnaire answers
Google's production access form asks what feedback you received and what you changed as a result. Vague answers get rejected. This section gives you specific, dated, device-attributed material to write from.
- Feedback received, quoted from the report above
- Updates shipped in response, with version codes
- Tester re-verification after each update
- Draft answers mapped to each question Google asks
Why the report decides your application
Google’s production access form asks two questions that most developers answer badly: what feedback did your testers give you, and what did you change as a result. Reviewers have read thousands of versions of “testers were happy, everything worked well.” That answer reads as evidence that no real testing happened.
A useful answer names devices, dates, and specific defects, then names the build you shipped in response. That is what the bug and feedback sections give you. Our guide to the production access questionnaire walks through how to write those answers.
Frequently Asked Questions
What exactly do I receive at the end of a TesterBee campaign?
Every campaign ends with a written report covering four areas: a device and engagement summary of your 14-day window, reproducible bug reports ranked by severity and priority, usability feedback consolidated across testers, and draft answers for the Google Play production access questionnaire. You keep the report.
Is this report the same for every plan, or does it depend on tester count?
The report format is the same at every tier. What changes with a higher tester count is the volume of feedback, because more testers on more devices surface more edge cases. Nothing in the report is withheld at the base tier.
Do I need the report if my app is already stable?
Google evaluates engagement, not just stability, and the production access questionnaire asks what feedback you received and what you changed. A stable app still needs a documented feedback loop to answer that question credibly. The report is what makes that answer specific rather than generic.
Can I use the report in my production access application?
Yes, that is what it is for. The questionnaire answers section is written to be adapted directly into Google Play Console. You are responsible for what you submit, so review and adjust the wording to match what actually happened in your app.
Start your campaign and get the real report
12 verified Android testers, 14 days of monitored engagement, and this report at the end. Flat $14.99 with 2–3 buffer testers included and no service fee.