XXX

Test Summary Report

Author: Albin Abraham

Version: 0.2
Date: 15 June 2010
Document Version Control

Version Date Description/notes Author(s)

Related Documents

Document Name Version Author

Approval and Sign off

Approver Name Role Date Signature

Document Circulation List

Approver Name Role Date Signature
 Table of Contents

1. INTRODUCTION 4
1.1 Project Background.......................................................................................4
1.2 Document Objectives....................................................................................4
2. TEST COVERAGE 5
2.1 Test Stages.................................................................................................5
2.2 What is tested..............................................................................................5
2.3 What is Not Tested.......................................................................................5
3. ASSESSMENT & RECOMMENDATION 6
3.1 Exit Criteria Evaluation..................................................................................6
3.2 Final Defect Status.......................................................................................6
3.3 Testing Status Evaluation..............................................................................6
3.4 Recommendation..........................................................................................7
3.5 Learning for Future Projects...........................................................................7
4. FINAL VARIANCE/DEFECT STATUS 8
4.1 Milestone Variations......................................................................................8
4.2 Defect Records.............................................................................................8
4.3 Open Defects...............................................................................................8
4.4 Defect Priorities/Severities.............................................................................8
4.5 Defect Trends..............................................................................................9
1. Appendix 1- Requirements Not Met But Business Agreed 10
1. Introduction

1.1 Project Background

The current XXX process provides .

Project ID 0262
Project Title Process Automation
Application Under Test Salesforce.com

1.2 Document Objectives

This document describes the final test summary report for the XXX project. The objectives of
this document are to:
Provide a formal document which describes the testing that is done on the system, testing
phases completed and the results of the testing we undertake for the project
This report also identified all the open defects and the status of each defect at the end of
testing.
Assessment of testing completion, and details risks identified during testing, and residual
risks for consideration before the go-live.
2. Test Coverage

2.1 Test Stages

Unit Functionality Integration

System Interface Performance
Regression Acceptance Pilot

2.2 What is tested

xxx
yyy
zzz

2.3 What is Not Tested

Xxx
Xxx
xxx
3. Assessment & Recommendation

3.1 Exit Criteria Evaluation

The table below represents the exit criteria mentioned in the test plan for this project.

Component Status Remarks

No P1 or P2 defects/issues open
No Priority-1 or Priority-2 defects
outstanding from System Testing and
UAT
All Medium and Low issues accepted 1 P-3 and 1P-4 defect open. Agreed
with the business and business is ok for
and signed-off
go-live even if this is not fixed.
Conditional sign-off given on 10th June.
Test Phase Summary completed and Full testing sign-off and summary
signed off
report in this document.

The status is denoted by RED, YELLOW or GREEN.

3.2Final Defect Status

Severity-1 Severity-2 Severity-3 Severity-4 Total

0 0 1 1 2
Open

3 30 59 7 99
Closed
3 30 60 8 101
Grand Total

3.3 Testing Status Evaluation

The table below represents the state of both the product and process. This table is explained in
the following sections.

Component Status Remarks

Quality of the test object The application is in a very good quality. Met more
than 99% of the business needs. Only 2 outstanding
issues which are of low priority.
Product Risks
No known product risks.

Testing Process Agile development methodology was used for the

project and testing followed the same process. Tight
communication between the tester, develop and
business owner and ensured all requirements are
delivered with good enough quality. Multiple test cycles
were executed and full regression testing is also done
after the completion of all defect fixes and retest.
Ready for Go-Live
Testing is completed. Development of all critical and
major functions is completed. System is ready for go-
live
The status is denoted by RED, YELLOW or GREEN.
3.4 Recommendation

Based on the test coverage, results analysis and evaluating the Exit Criteria defined for this
project, we recommend that the project progresses to the production. The Production
Acceptance should be done after the go-live.

3.5 Learning for Future Projects

1. Project Methodology and Development methodology should be closely aligned. Different

methods not recommended.
2. Involve the UAT in the earlier phases of the project for other projects. This will help to avoid
late changes in requirements.
4. Final Variance/Defect Status

4.1 Milestone Variations

Item Planned Actual Comments

Test Pan 21.05.2010 19.05.2010 Nil
Test Start Date 31.05.2010 26.05.2010 Started a bit early to familiarise with the system
A number of changes in the requirements and a
Test End Date 04.06.2010 10.06.2010 uncovered a number of defects. More test cycles
to ensure the quality.
Test Sign-of and
07.06.2010 15.06.2010 Delays in completing the testing
Summary
Go-Live Date 26.06.2010 No change No change envisaged
Total Testing Effort 140 hours 138 hours Under control

4.2 Defect Records

All defects that are logged as part of the testing as exported to a spreadsheet. It is available in
the project site at http://intranet/

4.3 Open Defects

Open defects are the defects that doesnt meet the requirement and behaves differently to what
business needs.

Defect Summary Severity Status Description

ID
Age (Days) field 4 Reopened Counting down should stop at 0. Low
40125
displaying negative priority though. This will not be fixed
values instead of and will go-live as a defect.
stopping at 0
Abc Tick Box needs to 3 Reopened Tried building a report with the DA
40373
be tracked for breach field. Doesn't show up. This
reporting should be fixed as part of the report
development this week. But can go-
live even if this is open.

4.4 Defect Priorities/Severities

Severity: Impact on the business operation . In other words, how bad is the defect? The
severity of defects is decided in consultation with the Business Consultant.

Defect Definition
Severity
Critical business functionality does not work, and no workaround exists.
Cannot launch until resolved.
Critical
Important business functionality does not work, and a workaround exists but
Major
has a significant business impact and is not sustainable. Cannot launch until
resolved.
Required business functionality does not work, but a workaround exists. Can
Moderate
launch without fix with approval from the business, with an agreed plan for
resolution.
Desired business functionality does not work, but a workaround exists. Can
Minor
launch without fix with approval from the business, with an agreed plan for
resolution or further investigation.
4.5 Defect Trends
Please find the trend of all defects raised as part of xxx project.