0% found this document useful (0 votes)
140 views7 pages

TSR-Test Summary Report

1. This document provides a test summary report for the <<project name>> project. It describes the test process, scope, results including number of defects, deviations from the test plan, and outstanding defects. 2. The key findings are: test cases covered 80% of planned scope with 80% of defects addressed. There were 8 outstanding high priority defects requiring resolution. 3. The recommendation is to proceed with deployment (Go) while addressing the outstanding defects according to the defined resolution plan. Improvements for future testing are also recommended.

Uploaded by

Ranjit Jain
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
140 views7 pages

TSR-Test Summary Report

1. This document provides a test summary report for the <<project name>> project. It describes the test process, scope, results including number of defects, deviations from the test plan, and outstanding defects. 2. The key findings are: test cases covered 80% of planned scope with 80% of defects addressed. There were 8 outstanding high priority defects requiring resolution. 3. The recommendation is to proceed with deployment (Go) while addressing the outstanding defects according to the defined resolution plan. Improvements for future testing are also recommended.

Uploaded by

Ranjit Jain
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

TEST SUMMARY REPORT

Author: Date: Signature:

<<Name>>

<<Designation>>

<<Department>>

Approval:

<<Name>>

<<Designation>>

<<Department>>

Internal Use Only


Approval Information in Annexure Z
Document History

Version Date Author Comments

1.0 <<dd-mon- <<Name>> <<Description>>


yyyy>>

Page: 2 / 7
Table of contents
1 BACKGROUND....................................................................................................................................4

1.1 PURPOSE.........................................................................................................................................4

1.2 DEFINITIONS, ACRONYMS AND ABBREVIATIONS........................................................................4

1.3 REFERENCES...................................................................................................................................4

2 ASSUMPTIONS.....................................................................................................................................5

3 TEST PROCESS....................................................................................................................................5

3.1 SCOPE DETAILS..............................................................................................................................5

3.2 TEST CASE SUMMARY RESULTS....................................................................................................5

3.3 RELEASE SUMMARY RESULTS........................................................................................................6

3.4 DEFECT SUMMARY RESULTS.........................................................................................................6

3.5 FEATURE-BASED SUMMARY RESULTS..........................................................................................6

4 DEVIATIONS........................................................................................................................................7

4.1 RESOLVED DEFECTS.......................................................................................................................7

4.2 OUTSTANDING DEFECTS...............................................................................................................7

5 RECOMMENDATION............................................................................................................................7

Page: 3 / 7
1 BACKGROUND
<Describe a brief background of the <<<project name>>> project and the particular phase for which
the completion report is prepared for>

Brief Application Overview

1.1 PURPOSE
This document is the test completion report for the <<<project name>>> project. The purpose of this
document is to:

 Serve as the final release document, confirming the end of all test levels for the <<<project
name>>> project in scope of the test plan (Ref: Conducting Tests section)

 Describe the tests performed during the <<project name>> project

 Describe any variance from the planned scope of testing

 Summarize defects logged and addressed during testing

 Summarize outstanding defects at the end of testing (based on triage outcome), providing
details of responsibility and planned timescales for resolution

 Describe conclusions (GO or No GO) drawn from test execution

1.2 DEFINITIONS, ACRONYMS AND ABBREVIATIONS


[This subsection should provide the definitions of all terms, acronyms, and abbreviations required to
properly interpret the Test Summary Report.  This information may be provided by reference to the
project Glossary.]

TERM / ABBREVIATION DEFINITION

<List all terms and abbreviations used in this document in this section. It is also permissible to
reference a glossary document, if one is being maintained and approved, and omit this section.>

1.3 REFERENCES
[This subsection should provide a complete list of all documents referenced elsewhere in the Test
Summary Report]

Page: 4 / 7
2 ASSUMPTIONS
Detail the assumptions made from relevant test plan of <<project name>>. Include additional
assumptions made during test activities (if any)

3 TEST PROCESS
Provide a summary of the quality of the test process as implemented. Provide an overall assessment
of the scope coverage, build or release tested, with a summary of the test results, including the
number of defects summarized by impact/severity level.

3.1 SCOPE DETAILS


Detail the scope coverage for the <<project name>> project

IN SCOPE OUT OF SCOPE

3.2 TEST CASE SUMMARY RESULTS


The following is a summary of the test case results obtained for the reported test effort.

Summary Assessment Total Test Cases Coverage Comments


Percentage

Planned Testcases <# planned testcases> <% total planned> <comments>

Executed Testcases <# executed testcases> <% total executed <comments>


testcases>

Passed Testcases <# passed testcases> <% total passed <comments>


testcases from
planned execution>

Failed Testcases <# failed testcases> <% total failed <comments>


testcases from
planned execution>

Pending Testcases <# pending testcases> <% total pending <comments>


testcases from
planned execution>

Page: 5 / 7
3.3 RELEASE SUMMARY RESULTS
The following is a summary of the release/iteration info obtained for the reported test effort.

Release No Release Date Covered Testcases Defects Comments


Features Covered (% - Coverage
Executed v/s (% - Open
Planned) v/s Total)

<release no> <<dd-mmm-yyyy> <scope> 80% (80/100) 80% (8/10) <comments>

3.4 DEFECT SUMMARY RESULTS


The following is a summary of the test incidents (i.e., unexpected results, problems, and/or defects)
that were reported during the testing:

Severity Total Total Total Total Total Comments


Level Defects Resolved Outstanding Rejected Deferred
Logged (FIXED) (OPEN & (Not a (Future
REOPEN) Defect) Release)

<Severity> <# total <# total <# total <# total <# total <comments>
reported> resolved> outstanding> rejected> deferred>

Total

3.5 FEATURE-BASED SUMMARY RESULTS


The following section summarizes the test cases employed for <module/function> and the test results
obtained for each test case

Module/Component/ Total Executed Testcases Outcome Comments


Testcases Testcases Coverage (PASS/FAIL)
Function/Page (%)

Module-1 <total <executed <executed PASS or FAIL


testcase> testcase >/<total>
out of
total>

Page: 6 / 7
4 DEVIATIONS
Provide a brief description of the unexpected results, problems, or defects that occurred during the
testing.

4.1 RESOLVED DEFECTS


Identify all resolved defects and summarize their resolutions.

4.2 OUTSTANDING DEFECTS


Identify all unresolved/outstanding defects (OPEN, REOPEN) and provide a plan of action for their
resolution.

5 RECOMMENDATION
Outcome of the triage and final release plan for deployment – Go/No Go to be expanded

Provide any recommended improvements in the design, operation, or future testing of the project
that resulted from the testing being reported. A discussion of each recommendation and its impact on
the business aspect of project may be provided. If there are no recommendations to report, then
simply state as such.

Page: 7 / 7

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy