Project:

Date: Week nr:

Template
Test Report

-1-
 Project:

Date: Week nr:

The italic text must be replaced with status information about the test project.

Summary
The summary chapter will discuss in brief the progress on test execution (percentage
of tests done) and the quality of the product (number of outstanding defects). Also
the opinion of the test manager is described regarding the feasibility of the release
data

Quality
The quality chapter will provide information on the quality of the software product
during the test execution phase. Most information used for the writing the quality
paragraph will be derived directly from QualityCenter. The testers are responsible for
updating the information in QualityCenter that will be used by the test manager. The
testers should record the defects in QualityCenter and track the status of the defects,
so at all times the status of the defects is accurate and known. The following statuses
are used: Showstopper, Critical and Serious.

Outstanding defects with status “OPEN” (at week number,…)

Subsystem Showstoppers1 Critical Serious Total

“Other”
Total

Defects found this week (week nr,..)

Subsystem Showstoppers Critical Serious Total

“Other”
Total

1
Showstopper: external, customer has serious problem with this defect
Critical defect: internal serious problem, customer has no problem
Serious defect: internal and workaround is possible

-2-
 Project:

Date: Week nr:

Progress Test execution

In the progress test execution chapter information will be provided on the progress
made on execution of the test scripts. Also the progress of the planning as described
in the test plan will be evaluated. Ambiguities will be mentioned. (Schedule: planned
versus actual and Effort: planned versus actual)

Executed tests per subsystem (week nr,…)

Subsystem Planned Tested Closed To do

“Other”
Total

Explanation of the used terms:

• Subsystem: (sub) system or module under test
• Planned: number of test scripts that will be executed
• Tested: number of test scripts executed
• Status “closed”: number of test scripts that have been executed and have no
remaining (outstanding) defects, i.e. expected outcome = actual outcome
• To do: numbers of test scripts that must be done or re-tested

The project manager will be notified via this paragraph the moment slippage occurs
on the estimated end dates of the plan.

-3-
 Project:

Date: Week nr:

Effort
In this chapter the effort will be discussed in terms of progress of the test activities
and time spent per person.

Progress test activities

In this chapter the progress on the test activities will be discussed

Act. Description Del. Person Start date End date #Hours Start date End date Hours To Dev. Status
ID ID planned Real Do

Time spend per person

In this chapter the time spent per person on test activities will be discussed. If
significant changes on time spent on activities are there they will be described in this
introduction.

Name Time planned Time spent To do Deviation

tester

-4-
 Project:

Date: Week nr:

Test Project Risks

The chapter Test Project Risks will provide information on risks that may occur during
the execution phase. The information can be gathered out of the following items:
Quality of the product [progress], Progress Test execution [planned, tested, to do and
result alright]. By tracking this information and make it an issue of the quality reports,
one can take preventive or corrective actions on risks that may occur.

# Risk description Likelihood Impact Trigger Contingency Status

Action
1
2
3
4

Annex
In this annex the current outstanding showstoppers are described (sorted by
number), to be discussed during the quality and progress meeting.

-5-