How-to
What's in a closed testing final report, and where it helps in the production access questionnaire
When your closed test ends, we compile the device run records from the whole test into a single report. We go through what it contains and which questionnaire question each item supports. You can open a realistic sample report.
Last checked Oct 13, 2026.
A report is a record, not a memory
You end up writing the production access questionnaire a few days after testing ends. If you write it from memory, you get vague answers like “Testing went well,” and that leads to rejection. What you need is when, how many devices, how many times, and what didn't work.
When the 14 days of closed testing end, DUIRE compiles the device run records from that period into a single report. The actual page is public, so feel free to take a look first.
View a sample report
It's the same page customers get. The numbers are sample data, and printing and PDF download work just the same.
Open the sample reportWhat's inside
- At a glance — installed devices, successful run rate, main screen reach rate, number of updates, number of issues found
- Summary — what happened during the period, written out in sentences
- Runs by date — how many times the app was run each day over 14 days, and how many succeeded
- Version history — which version was detected on which day and how many devices it reached
- Device table — run success rate and main screen reach rate by model and Android version
- Issue log — time, device, and error for each failed run
- First-launch path and screenshots — the screens the app went through when it first opened
- Questionnaire reference — the question-by-question facts explained below
Where it fits in the questionnaire
The last page of the report is a reference for the production access questionnaire. For each question, we attach facts pulled from our records. Don't copy them as is — write your own sentences based on those facts.
| Report item | Questionnaire question it supports |
|---|---|
Test period and number of installed devices The period and device count are the evidence that you met the requirement. Just carry over the dates and how many devices stayed installed. | How you recruited testers and how engaged they were |
Daily run log (by date and device) Run counts and success rates are recorded as numbers. Instead of “they used it consistently,” you can write something like “504 runs over 14 days, 99.6% successful.” | Describe the engagement you received from testers |
Main screen reach rate An app that's merely installed is different from one that opened to its first screen. You can answer while separating what was and wasn't confirmed. | Whether testers used your app's features |
Install history by version This is where approvals are most often won or lost. With a record of which version shipped on which day and how many devices it reached, you can answer specifically. | How you applied what you learned in testing to your app |
Failed runs with device and OS Finding and fixing a problem is the best answer. What didn't work on which device becomes your evidence as is. | Summarize the feedback you collected |
First-launch path and per-device screenshots You can show on screen that the first screen loaded correctly across multiple manufacturers and OS versions. | Why you believe your app is ready for production |
For examples of how to turn these into sentences for each question, see How to answer the production access questionnaire. If you're rewriting after a rejection, read it alongside 7 reasons for rejection.
Our rule: no embellishment
This report contains only records of automated runs on devices. We don't present them as feedback from human testers, and we don't write your questionnaire answers for you. Making up experiences that never happened and submitting them puts your developer account at risk, not just your app.
Frequently asked questions
- When do I get the report?
- When the 14 days of closed testing end, you can view it on the final report tab in your dashboard and download it as a PDF. Before you meet the requirement, it's shown as an interim record.
- Do I submit the report to Google?
- It isn't a document you submit. It's supporting material for you to use when answering the production access questionnaire yourself. There's no field for attaching the report itself.
- Do you write the questionnaire answers for me?
- No. Making up tester experiences that never happened and submitting them puts your developer account at risk. The report lays out only the facts, and you write the answers yourself.
- Does it include tester reviews?
- No. It contains only the records of automated runs on devices. Not dressing them up as human feedback is the principle behind this report.
Meet the requirement without recruiting testers
DUIRE joins your closed test with real Android devices and opens your app every day for 14 days. Registering your app and checking installability are free.