Which items should be included in a test summary report?

• A. The timestamps of test runs.
• B. Only the number of tests executed.
• C. The source code changes only.
• D. Overall pass rate, critical defects, risk areas, open items, and recommendations for release.

Answer: (D)

A test summary report should give stakeholders a clear snapshot of testing status and readiness for release. The best choice includes the elements that communicate overall quality and what actions are needed: the overall pass rate shows how much of the tested work meets criteria; critical defects highlight showstoppers that could block release; risk areas flag where quality is uncertain; open items indicate what still remains to be done; and recommendations for release provide concrete guidance for next steps.

Timestamps of test runs are useful for traceability, but they don’t by themselves convey the level of quality or risk. The number of tests executed is too narrow to indicate how well the product meets requirements. Source code changes belong more to development and version control, not to the testing status and release decision. Combining the key quality indicators with actionable release guidance gives a complete and practical picture for deciding whether to proceed.