Test report
A test report is the document that summarises a testing cycle for the people who will decide on it: what was tested, on which build and environment, how many tests passed, failed or were blocked, which defects are open and how serious they are, what was not tested and why, and the tester's assessment of whether the build is fit to release. It is written for a decision.
The longer version
The report is built from the execution log but is not the log. It names the scope: the build, the environment, the requirements or features in the cycle. It gives the counts by outcome, and then the part the counts cannot carry: the open defects listed by severity, the areas that were blocked or deliberately skipped, the risks the tester sees, and a recommendation. A good report can be read in a few minutes by a product manager and answers the question they came with, which is whether to ship, and if not, what stands in the way.
Three documents get confused. The execution log is the raw record, one row per test per run, and it is data, not a report. The test report summarises one cycle, and there may be one per sprint or per build. The test closure report summarises the whole test effort at the end of a project or release, with lessons and metrics across cycles, and is written once. A daily status email during execution is none of these; it is a progress note and should not be mistaken for the assessment.
A report that is only counts misleads. Ninety-eight passes and two failures reads as nearly done until the two failures turn out to be the login and the payment. A report that omits what was not tested invites the reader to assume everything was. And a report with no recommendation pushes the decision back to a reader with less information than the writer. The tester's judgement is the payload; the counts are the evidence for it, and the open defects, each with its evidence attached, are what the reader will go and look at.
Common questions
What should a test report contain?
The scope: build, environment, features and requirements covered. The results: tests passed, failed, blocked and not run. The defects: open ones by severity, with links. The gaps: what was not tested and why. The risks the tester sees, and a clear recommendation on whether the build is fit to release. Everything else is appendix.
What is the difference between a test report and a test closure report?
A test report summarises one testing cycle, such as a sprint or a release candidate, and is written for the decision about that build. A test closure report summarises the entire test effort for a project or release once testing is finished, covering all cycles, the exit criteria, the defects left open, and what to do differently next time.
Who writes the test report and who reads it?
The test lead or the tester who ran the cycle writes it, because the assessment needs first-hand knowledge. The readers are the people making the release decision: the product manager, the engineering lead, sometimes the client. The report is written for them, in their vocabulary, with the raw log available for anyone who wants it.
When is a test report written?
At the end of each test cycle, once every planned test has an outcome and the defects found have been logged and assessed, and before the release decision the report exists to inform. Writing it earlier reports on a cycle that has not finished; writing it after the decision makes it a record rather than an input. Many teams also send a daily status note during execution, which is progress, not the report.
What is a test summary report?
A test summary report is the same document under the name the IEEE test documentation standard uses for it: the summary of a testing cycle written for the people who will decide on the build. Some teams use summary report for the per-cycle document and test report for a per-run or per-suite result, but the content is the same: scope, outcomes, open defects, gaps, risks and a recommendation.
Bug reports that arrive ready to triage.
Collect replay, console, network and browser context with the Free plan.