Test progress report
A regular report during testing that communicates status against plan, blockers, new risks, and upcoming work to support control.
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 progress report in a practice question
Question 1
What distinguishes a test progress report from a test completion report?
- Progress reports are produced by the test team; completion reports by the stakeholders
- Progress reports support ongoing test control; completion reports summarize a finished test activity
- Progress reports record defects; completion reports record the metrics that were collected
- 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
Question 2
At a weekly checkpoint, testing is behind schedule and a new product risk has appeared. Which report and purpose best fit this situation?
- A completion report, to accept the work product before the test activity ends
- A progress report, to support ongoing control and possible changes to schedule, resources, or plan
- A completion report, because only completion reports may contain deviations from the test plan
- A progress report, to consolidate lessons learned after the test activity has ended
Show answer
- A completion report, to accept the work product before the test activity endsCompletion reporting occurs when a project, test level, or test type is complete, not at this weekly checkpoint.
- Correct answer: A progress report, to support ongoing control and possible changes to schedule, resources, or planProgress reporting supports ongoing control when deviations or changed risks require adjustments.
- A completion report, because only completion reports may contain deviations from the test planBoth progress and completion reports can contain deviations; deviations are not exclusive to completion reports.
- A progress report, to consolidate lessons learned after the test activity has endedConsolidating lessons learned after testing is a completion activity, not the purpose of weekly progress reporting.
A test progress report supports ongoing test control and provides enough information to change the schedule, resources, or test plan when deviations or changed circumstances require it. It typically reports progress including notable deviations and new or changed risks. A completion report summarizes a completed test activity and may also contain deviations.
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®.