Skip to content
← All CTFL glossary terms

Test completion report

A summary of a completed stage of testing, including an evaluation against exit criteria and lessons learned.

Syllabus chapters: 5

Sources: ISTQB® Certified Tester Foundation Level syllabus 4.0.1 and the official ISTQB® Glossary. Glossary content © International Software Testing Qualifications Board; source: glossary.istqb.org.

Related terms

Test completion report in a practice question

Question 1

Which of the following is an example of an ENTRY criterion for test execution?

  1. All planned tests have been executed
  2. The defect backlog contains no critical open defects
  3. The test environment is available and configured
  4. The test completion report has been approved
Show answer
  • All planned tests have been executedHaving executed all planned tests is an exit criterion, not an entry condition.
  • The defect backlog contains no critical open defectsA clean critical-defect backlog is an exit criterion for completing testing.
  • Correct answer: The test environment is available and configuredA ready, configured test environment is a precondition — an entry criterion.
  • The test completion report has been approvedApproval of the completion report happens at the end, so it is an exit criterion.

Entry criteria define preconditions for starting an activity — e.g. testable requirements available, environment ready, test data prepared. Executed tests, defect thresholds, and achieved coverage are typical exit criteria.

Syllabus section 5.1.3

Question 2

What distinguishes a test progress report from a test completion report?

  1. Progress reports are produced by the test team; completion reports by the stakeholders
  2. Progress reports support ongoing test control; completion reports summarize a finished test activity
  3. Progress reports record defects; completion reports record the metrics that were collected
  4. Progress reports follow a set template; completion reports are informal and ad hoc
Show answer
  • Progress reports are produced by the test team; completion reports by the stakeholdersThe test team generates progress reports for stakeholders to keep them informed.
  • Correct answer: Progress reports support ongoing test control; completion reports summarize a finished test activityOngoing control against summarizing a completed test activity.
  • Progress reports record defects; completion reports record the metrics that were collectedBoth report types include metrics; neither is limited to recording defects.
  • Progress reports follow a set template; completion reports are informal and ad hocThis is the wrong way round: completion reporting follows a set template.

Test progress reports support the ongoing test control and must provide enough information to modify the test schedule, resources or test plan when circumstances change. A test completion report is prepared during test completion, when a project, test level or test type is complete and its exit criteria have ideally been met, and summarizes that activity. Test progress reporting within a team is often frequent and informal, while completion reporting follows a set template and occurs only once.

Syllabus section 5.3.2

Original PrepBench practice material, not official exam questions or exam dumps. PrepBench is independent and is not affiliated with or endorsed by ISTQB®.