Test Closure Report

Author: Matthew Cunliffe

Date: 5th March 2012

Version 1.0

http://www.euro-point.co.uk

Contents

1. Document Control	3

1.1 Document History	3

1.2 Document Distribution	3

1.3 References	3

2. Introduction	4

2.1 Document Purpose	4

2.2 Executive Summary	4

3. {test phase} Testing	5

3.1 Test Coverage	5

3.2 Software Delivery	5

3.3 Test Execution	5

4. Progress	6

4.1 Test Progress	6

4.2 Resource Utilisation	6

5. Outcome	7

6. Defects	8

6.1 Defect Management	8

6.2 Defects found during {test phase} Testing	8

7. Summary and Conclusions	9

7.1 Process Problems	9

7.2 Risk Assessment	9

7.3 Detailed Recommendations	9

7.4 Additional Tests Required	9

APPENDIX A	– Outstanding Retests	10

APPENDIX B	– Outstanding Defects	11

Document Control

Document History

Date	Version	Details	Author
dd/mm/yyyy

Document Distribution

Title	Person	Role
Project Manager	Approver
Test Manager	Accountable & Responsible
Business Lead	Approver
Business Analyst	Consulted
Requirements Lead	Consulted
Build Manager	Consulted
Architect Lead	Consulted
Release Manager	Consulted
Project Team	BA Team Test Team Config Management Team	Informed

References

The following documents were used in creation of this document:

Ref	Document Title	Version	Location
1	Product Description for Test Closure Report
2	Release Management Plan
3	Defect Management Approach
4	Document & Configuration Management
5	Change Control Process
6	High Level Scope Document
7	Quality Assurance Process
8	Risk Register
10	{test phase} Approach
11	Regression Test Approach

Introduction

This document is the {test phase} Test Closure Report for the {project} programme delivery. It provides details of the completion status of the {test phase} Test stage. The {project} programme delivery introduced functionality to {high level description of functionality}.

Document Purpose

The information within this report details the completion status of the {test phase} Test phase. It includes the test run results and the defect management summary that has been derived from the {Europoint Dashboard}.

Executive Summary

{The system is fit for purpose. No Critical or High Business Severity defects remain open and no Very High or High Technical Priority defects remain open. All tests have been executed and have been completed successfully.}

{The system is not fit for purpose. {xx} Critical/High Business Severity defects remain open and {xx} Very High/High Technical Priority defects remain open. {xx} tests could not be completed as a result. It is recommended that:

Recommendation 1

Recommendation 2}

See section 7.3 for the detailed recommendations.

{test phase} Testing

Test Coverage

A number of test scenarios were identified to run through the discrete functional areas that comprise the delivery. The high level scope covered in {test phase} was as follows:

Functionality 1

Functionality 2

Some {test phase} Area

{A description of the {test phase} area.}

Software Delivery

The software was delivered into Configuration Management (CM) by the development teams on a scheduled basis, incorporating releases comprising additional functionality and defect resolutions. A release note was provided with each release, identifying the functionality and defect resolutions contained within the release, together with deployment details, release content details and any outstanding issues.

Following receipt into CM, an entry gateway meeting was held to confirm that the entry criteria for the {test phase} had been met. The software was then passed to the deployment teams and scheduled for implementation on the {test phase} Test environment.

Following the completion of test execution, an exit gateway meeting was held to confirm that the exit criteria for the {test phase} had been met. Following agreement from all stakeholders, the test phase was exited, and this report produced.

Test Execution

Test execution was carried out by professional Test Analysts on the {test phase} environment using both manual and automated test scripts. {Two/Three} cycles of test execution were carried out to ensure 100% coverage.

The test execution cycle was planned and resourced in a controlled way. The resource allocation was kept under review to ensure that both quality and quantity were maintained throughout.

Progress

Test Progress

The following graph shows the progress of {test phase} Testing to {date}. The test execution was completed within the planned timescales with the identified resource allocation.

{insert graph here}

Figure 31 – {project} {test phase} Testing Progress

Resource Utilisation

The table below shows the estimated and actual effort spent on the testing activity. The estimated effort is taken from the Test Estimate, reference: {document name}. The actual effort is taken from the work recording system. Both figures are specified in man-days.

Resource Type	Estimated Effort	Actual Effort	Variance	Reason for Variance
Test Analyst	0.00
Data Analyst	0.00
Total:	0.00	0.00	0.00

Outcome

The {test phase} tests have been carried out on the {test phase} Test environment. There were three test phases:

Sanity/Smoke Testing – Sanity tests were carried out following the installation of each major release to ensure that the applications had been correctly installed and were in a suitable state for {test phase} testing to commence.

{test phase} Testing – {test phase} tests were carried out to check that the applications had been correctly redelivered, that the integrity and configuration of the software was correct, and that any faults that were identified were raised.

Regression Testing – Regression testing was carried out to ensure that new functionality and resolved defects did not regress any existing functionality or introduced further defects in the system.

The results of these test phases are presented below.

Test Phase	Planned Tests	Executed Tests	Tests Passed	Tests Failed	% Complete
Sanity Testing	100%
Sanity Retesting	100%
Regression Testing	100%
Regression Retests	100%
{test phase} Testing	100%
{test phase} Retests	100%
Totals	0	0	0	0	100%

All planned tests were executed, with a number of retests remaining outstanding. {xx} {test phase} retests remain outstanding as they are associated with defects that have been deferred beyond the go-live date of {project}. {xx} Regression retests remain outstanding for the same reason. These tests will therefore not be completed within the {project} timescales. These are details in the appendices.

Defects

Defect Management

During the execution of {TEST PHASE}, defects were logged in Quality Centre. Through the Defect Management Process the defects were monitored and actions put in place to resolve them initially; the defect was then assigned a Development priority if it was application related.

Defects found during {test phase} Testing

{xx} defects were raised during the test process, of which {xx} are outstanding as at {date} and are currently being managed through the defect resolution process.

The following tables show the defects identified during {test phase} Testing to {date}.

{insert graph here}

Figure 51 – {project} {test phase} Test Defects By Status

{insert graph here}

Figure 52 – {project} {test phase} Defects by Business Severity

{insert graph here}

Figure 53 – {project} {test phase} Defects by Technical Priority

{insert graph here}

Figure 53 – {project} {test phase} Defects by Root Cause

{insert graph here}

Figure 53 – {project} {test phase} Defects by Defect Fix Resolution

Summary and Conclusions

{{xx} retests outstanding of which {xx} are {test phase} and {xx} are regression-based tests. Each of these has been associated with a defect that has been scheduled for delivery outside the initial {project} date of {date}. It has been identified that these defects do not prevent operation in the Production environment and will be scheduled according to impact.}

Process Problems

{Identify here any problems which were encountered during test execution, e.g. failure of systems, lack of IT support, test procedures etc.}

Risk Assessment

{Specify any perceived risk that would materialise if this software were used in its present state and the likelihood of that risk occurring.}

Detailed Recommendations

{Detail any specific recommendations based on the defects raised, the root cause/defect fix resolution for the defects, the tests executed etc).

Additional Tests Required

{List any new test scenarios or test cases that have been identified as a result of this testing activity.}

– Outstanding Retests

The following retests remain outstanding:

#	Test Case	{test phase} Area	Related Defect #

– Outstanding Defects

The following defects remain outstanding:

#	Description	{test phase} Area	Raised On	Status	Technical Priority	Business Severity

End of Document

Includes ad hoc re-tests. Failed tests have been subsequently re-tested and passed.