Home Resources FREE EBooks QA Testing  Courses  Automation 

Types Of Testing  Tutorials  Data 

Home Resources FREE EBooks QA Testing  Courses  Automation 

Types Of Testing  Tutorials  Data 

How To Write An Effective Test Summary Report [Sample

Report Download]
Last Updated: November 29, 2021

A Simple 12 Step Guide to Write an Effective Test Summary Report with Sample Test Summary Report
Template:

Several documents and reports are being prepared as part of Testing. Some are Test Strategy doc, Test
Plan doc, Risk management Plan, Configuration management plan, etc. Among these Test Summary
Report is one such report which is prepared after the Testing is completed.

I have tried to explain the purpose of the ‘Test Summary Report’ and provided a sample Test Summary
Report template along with an actual report for download. 

What You Will Learn: [hide]

What is a Test Summary Report?

12 Steps Guide To Writing An Effective Test Summary Report
Few Points To Note While Preparing The Test Summary Report
Conclusion 
Recommended Reading
What Is A Test Summary Report?
As we know, Software Testing is an important phase in SDLC and also it serves as the “Quality Gate” for
the application to pass through and certified as “Can Go Live” by the Testing Team.

Test Summary Report is an important deliverable which is prepared at the end of a Testing project, or
rather after Testing is completed. The prime objective of this document is to explain various details and
activities about the Testing performed for the Project, to the respective stakeholders like Senior
Management, Client, etc.

As part of Daily Status Reports, daily testing results will be shared with involved stakeholders every day.
But the Test Summary Report provides a consolidated report on the Testing performed so far for the
project.

Recommended reading => How to Report Test Execution Smartly (Status Report Template download)

Assume that if the Client who sits in a remote location needs to understand the results and status
about a Testing project which was performed for a period of, say for example – four months, Test
Summary Report will solve the purpose.

This is also an artifact required to be prepared as part of the CMMI process.

What Test Summary Report Contains?

A typical Test Report template will contain the below information, however, based on each Company’s
format & practice, the contents may vary. I have also provided real examples for better understanding.

At the end of this article, you can download a Test Summary report sample.

12 Steps Guide To Writing An Effective Test Summary Report

Step #1) Purpose of the document

<Short description of the objective of preparing the document>

For Example,  This document explains the various activities performed as part of the Testing of the
‘ABCD Transport System’ application.

Step #2) Application Overview

<Brief description of the application tested>

For Example, ‘ABCD Transport System’ is a web-based Bus ticket booking application. Tickets for various
buses can be booked using the online facilities. Real-time passenger information is received from a
‘Central Repository System’, which will be referred before booking is confirmed. There are several
modules like Registration, Booking, Payment, and Reports which are integrated to fulfill the purpose.

Step #3) Testing Scope

1. In Scope 
2. Out of Scope
 3. Items not tested

<This section explains the functions/modules in scope & out of scope for testing; Any items which are
not tested due to any constraints/dependencies/restrictions>

For Example, A functionality verification that needs connectivity to a third party application cannot be
tested, as the connectivity could not be established due to some technical limitations. This section
should be clearly documented, else it will be assumed that Testing covered all areas of the application.

In-Scope: Functional Testing for the following modules are in Scope of Testing
Registration
Booking
Payment
Out of Scope: Performance Testing was not done for this application.
Items not tested: Verification of connectivity with the third party system ‘Central repository
system’ was not tested, as the connectivity could not be established due to some technical
limitations. This can be verified during UAT (User Acceptance Testing) where the connectivity is
available or can be established.

Step #4) Metrics

<Metrics will help to understand the test execution results, the status of test cases & defects, etc.
Required Metrics can be added as necessary. Example: Defect Summary-Severity wise; Defect
Distribution-Function/Module wise; Defect Ageing etc.. Charts/Graphs can be attached for better visual
representation>

No. of test cases planned vs executed

No. of test cases passed/failed

No of defects identified and their Status & Severity


 Defects distribution – module wise

Step #5) Types of testing performed

1. Smoke Testing
2. System Integration Testing
3. and Regression Testing

<Describe the various types of Testing performed for the Project. This will make sure the application is
being tested properly through testing types agreed as per Test Strategy.

Note: If several rounds of testing were done, the details can also be included here.>

For Example,
a) Smoke Testing
This testing was done whenever a Build is received (deployed into Test environment) for Testing to make

sure the major functionality is working fine, Build can be accepted and Testing can start.
b) System Integration Testing

This is the Testing performed on the Application under test, to verify the entire application works
as per the requirements.
Critical Business scenarios were tested to make sure important functionality in the application
works as intended without any errors.

c) Regression Testing

Regression testing was performed each time a new build is deployed for testing which contains
defect fixes and new enhancements if any.
Regression Testing is being done on the entire application and not just the new functionality and
Defect fixes.
This testing ensures that existing functionality works fine after defect fix and new enhancements
are added to the existing application.
Test cases for new functionality are added to the existing test cases and executed.

Step #6) Test Environment & Tools

<Provide details on Test Environment in which the Testing is carried out. Server, Database, Application
URL, etc. If any Tools were used like Quality Center (now HP ALM) for logging defects>

For Example,

Step #7) Lessons Learned

<This section is used to describe the critical issues faced and their solutions (how they were solved
during the Testing). Lessons learned will help to make proactive decisions during the next Testing
engagement, by avoiding these mistakes or finding a suitable workaround>

For Example,

Step #8) Recommendations

<Any workaround or suggestions can be mentioned here>

For Example,

 Admin control for defect management tools can be given to Offshore Test manager for providing
access to the Testing team.
Each time the onsite Admin need not be contacted for requests whenever they arise, thereby
saving time due to the geographical time zone difference.

Step #9) Best Practices

<There will be a lot of activities done by the Testing team during the project. Some of them could have
saved time, some proved to be a good & efficient way to work, etc. These can be documented as a ‘Value
Add’ to showcase to the Stakeholders>

For Example,

A repetitive task done manually every time was time-consuming. This task was automated by
creating scripts and run each time, which saved time and resources.
Smoke test cases were automated and the scripts were run, which ran fast and saved time.
Automation scripts were prepared to create new customers, where a lot of records need to be
created for Testing.
Business-critical scenarios are separately tested on the entire application which is vital to certify
they work fine.

Step #10) Exit Criteria

<Exit Criteria is defined as a Completion of Testing by fulfilling certain conditions like

(i) All planned test cases are executed;
(iI) All Critical defects are Closed etc.>

For Example,

All test cases should be executed – Yes

All defects in Critical, Major, Medium severity should be verified and closed – Yes.
Any open defects in Trivial severity – Action plan prepared with expected dates of closure.

No Severity1 defects should be ‘OPEN’; Only 2 Severity2 defects should be ‘OPEN’; Only 4 Severity3
defects should be ‘OPEN’. Note: This may vary from project to project. Plan of Action for the Open
defects should be clearly mentioned with details on when & how they will be addressed and closed.>

Step #11) Conclusion/Sign Off

<This section will mention whether the Testing team agrees and gives a Green signal for the application
to ‘Go Live’ or not after the Exit Criteria was met. If the application does not meet the Exit Criteria, then
it can be mentioned as – “The application is not suggested to ‘Go Live’. It will be left with the decision
of Senior Management and Client and other Stakeholders involved to take the call on whether the
application can ‘Go Live’ or not.>

For Example, As the Exit criteria were met and satisfied as mentioned in Section 10, this application is
suggested to ‘Go Live’ by the Testing team. Appropriate User/Business acceptance testing should be
performed before ‘Go Live’.

Step #12) Definitions, Acronyms, and Abbreviations


<This section mentions the meanings of Abbreviated terms used in this document and any other new
definitions>

=> Download Sample Test Summary Report:

Click here to download a sample Test Report template with an example.

Few Points To Note While Preparing The Test Summary Report

As part of Test Execution, collect all required information on the Testing performed. This will help
to prepare a sound Test summary report.
Lessons learned can be explained in detail, which will convey the Responsibility which was taken
to solve these issues. Also, this will be a reference for upcoming projects to avoid these.
Similarly, mentioning the Best Practices will portray the efforts taken by the team apart from
regular testing, which will also be treated as a “Value Addition”.
Mentioning the Metrics in graphics form (Charts, Graphs) will be a good way to visually represent
the status & data.
Remember, the Test summary report shall mention and explain the activities performed as part of
the Testing, to the recipients to understand better.
A few more appropriate sections can be added if required.

Conclusion
The Test summary report is an important deliverable and focus should be to prepare an effective

document, as this artifact will be shared with various stakeholders like senior management, client, etc.
After performing exhaustive testing, publishing the test results, metrics, best practices, lessons learned,
conclusions on ‘Go Live’ etc. are extremely important to produce that as evidence for the Testing
performed and the Testing conclusion.

We have also made available the Test Report sample for download. It is a perfect example of how to
prepare an effective Test Summary report!

About the author: This is a guest post by Baskar Pillai. He is having around 14 years of experience in Test
management and the end to end software testing. CSTE certified Testing professional, trainer, worked in
IT majors like Cognizant, HCL, Capgemini and currently working as Test Manager for a large MNC.

Please let us know your Comments/questions/thoughts.

Recommended Reading
How to Write Software Testing Weekly Status Report
Sample Template for Acceptance Test Report with Examples
How to Report Test Execution Smartly – [Download Status Report Template]
Sample Test Case Template with Test Case Examples [Download]
Software Testing Documentation Guide (Why It's Important)
How to Write a Good Bug Report? Tips and Tricks
6 Most Important Steps to Make Your Test Reports Even Better
How To Write Test Strategy Document (With Sample Test Strategy Template)

 Software Testing Templates, Testing Tips and Resources

 Getting Started with Robotium – The Most Popular Android Application UI Testing Tool
 ETL vs. DB Testing – A Closer Look at ETL Testing Need, Planning and ETL Tools

52 thoughts on “How to Write an Effective Test Summary Report

[Sample Report Download]”

Vijay STH Founder

Please download the sample test summary report from following page:
https://www.softwaretestinghelp.com/wp-content/qa/uploads/2014/06/Sample-Test-Summary-
Report-by-SoftwareTestingHelp.pdf

Reply

Rameez

Sample Test Summary Report is missing.

Reply

Sheetal

Cannot download the Test Summary Report

Reply

Vijay STH Founder

@Rameez, Sheetal – added the download link in article as well as in the comment. Sorry for
inconvenience. There was an issue with our servers.

Reply

selvam

Really awesome !!!

Reply

savitha

Hi,
I am into Embedded testing with 4 yrs of experience. I have very gud experience in Manual
testing.
Good knowledge Selenium and Perl(not used much in the projects as it is more of manual
testing).
I am not getting interview calls.
Can u plz let me knw the current trend so that i can update on it.
Thank u

Reply

Vamsi

The Information shared is Very Good and Useful the people promoting to senior’s.

Reply

kote

Is it just me or I still have no luck downloading the file, getting the “Server not found” error.

Reply


Baskar Subramanian
 @Selvam, Vamsi-Thanks for the feedback.
@Savitha- Tools like Selenium, QTP, Loadrunner has steady scope. You can also focus on ETL
testing which has demand recently. SAP, Peoplesoft, Datawarehouse etc testing too have their
own share of demand.
For Automation tools – focus on the scripting part more.

Reply

Latha

Any one plz explain ETL testing ? How to learn it?

Reply

Baskar Subramanian

@Latha: There is an article titled “ETL vs. DB Testing – A Closer Look at ETL Testing Need,
Planning and ETL Tools” published in SoftwareTestingHelp.
You can also search for similar subjects in the website.

Reply

Santhosh-SVS

Super Ji Super Ji

Reply

karthick

Article is really informative,Especially Metrics.Please update some Sample Test Summary

Report.it might helpful for one look into it….Great…

Reply

Baskar Subramanian

@Karthick: Check Step#12 above – “Download Sample Test Summary Report:”

Reply

Suresh Kumar KSR


 Hi Sir,
It is great to everyone know about the test summaries even Developers. keep on posting your
valuable article’s.

Reply

Ravindra

Thanks Baskar.

I have been following this website for years to read new topics and enhance my knowledge in
Testing. This article is very valuable as each release requires an execution summary. Keep
posting !!

Reply

Jaya

Many Thanks Baskar for writing such a nice post, It’s really awesome.

Reply

Bala

Wow. Great! Excellent posting !

Reply

Edwin

Excellent Sir.

Reply

Baskar Subramanian

@Suresh,Ravindra,Jaya,Bala,Edwin: Thanks for your feedback!!!

Reply

RAVI KUMAR VERMA

Few peoples are there who take the ownership and move this ship ahead! 
You are one of them.
 Appreciated! Great Article

Reply

Baskar Subramanian

@Ravikumar verma: Thanks Ravi

Reply

Akhil

sample templat for mobile,land line phone,notepad,test cases please replay me

Reply

Abhishek

I am working as BA, BNFS vertical..

Recently Client ask me to prepare template ‘Summary Test case’. I gone through your post and it
realy awesome & Helpful.

Bhaskar, Pls keep posting..

Reply

Ganesh

please keep in mind..the purpose of testing is NOT just to validate what is written in Functional
Specification document, but to ensure the tested application is “Fit for Purpose” (FFP).

Reply

Sumedha

This is not a Test Summary Report. As per the IEEE 829 standard Test Summary Report
Template is as follows:

Test summary report identifier

Summary
Variances
Comprehensive assessment
Summary of results
Evaluation
Summary of activities

Approvals
 Reply

Baskar Subramanian

@Abhishek-Good that this post helped you..Sure will try posting more..
@Sumedha – There are many formats followed in companies. This is one such format. Summary
Report can be tailored to suit project requirements.

Reply

krishna

i have an experience in manual testing around 3 years and after experience i atten 2 interviews
but i don’t know how to explain my work experiece

Reply

Hussain

Very nice article as I was in search for a template for use in an UAT report. I am managing
different IT projects, which are run by our vendors, as I have a position in a Govt. Sector
Services oriented department. I am Mcs recently, can anyone guide me about, If I need to jump
into the field of Testing Software etc. Thanks

Reply

Sachin

Hi Sir,

Are test summary report and test closure same??

Please reply.

Reply

Kv

Awesome website and very nice blogs . Thanks a Lot , helping a lot

Reply

Nagaraj 
Now i am started my carrier in manual testing, what should i learn further.
 Reply

Meena

Awesome website,very helpful

Reply

santosh

Very informative article. Got what I needed. Thanks :)

Reply

Atiana

Can you please create the test summary report that you have so clearly articulated in an excel
format. I have been reading your online help for years and this is one my favorite articles.
Creating a test report excel including a dashboard, would be extremely helpful for those starting
out as well as those who work in companies that do not have process; your report then can be
use as a proof of concept to show testing status and hence the decision to setup and install
TestLink.

Reply

Baskar

@Sachin: test summary and test closure are somewhat similar.It confirms completion of
Testing.

Thanks to all for your feedback..

Reply

Baskar

@Atiana: Thanks for your feedback and suggestions. That’s a nice request. I do have few excel
formats.These excel reports will be easy to create charts and graphs and of course Dashboards
like.. Etc. If anyone still needs the copy pls email to [email protected].

Reply

pradip 
 hi this article is very useful to me and you guys provide very good explanation with
example.actually i don’t have any experience in testing but want to test my project for checking
load balance.so which test i should have to used for that and using which tools? if is there any
free tools please let me know. Thank you

Reply

Baskar

@Pradip – You can try Loadrunner for Load testing.

Reply

sonu singh

Try to testing rubber conveyor belt. But how much test. And how to test i should have to used
for that and using which tools?plz friends provide me knowledge if having
Thanks guys

Reply

Prasenjit

The document is really good and it will help if some provide some PPT it will give some clear
picture…anyway the content is great..

Reply

priya

Really good document.

Reply

J.Devi

I am finding this article quite neat and useful to you all for the same.
Thanks again.

Reply

Lily

 Thank you very much!
It help me a lot !

Reply

Oskar Kindbom

About Metrics:
Metrics are often requested by management, but are usually useless and should be avoided.
Think about what value the information has, e.g. “We planned 234 test cases, executed 198, 190
passed and 8 failed”. Does that mean anything? Were the 8 failures important or trivial? Are 234
test cases better than 233? Why did we not plan 235 test cases? etc, etc.
It’s better to tell the story, e.g. “The ‘edit’ function fails frequently, even for basic scenarios
which causes a poor user experience and loss of data. ‘New application process’ is working well
and the interface is easy to understand. Minor performance issues were observed with multiple
users accessing the application, but due to budget restrictions we could not perform proper
load testing.”

Reply

Mounica P

This is very helpfull.

Thank you

Reply

Ramzan Rasool

a company asked me to appear for preliminary selection testing exam of two hours. This is what
they will be examining for:
“Testing for this position includes the following:
Test Format
Basic Word Automated
Basic Excel Automated
Business Writing Manual

They will be checking MS WORD and EXCEL skills in automated format. I am not so sure what
that entails. Does anybody have an idea. The position i applied for is “Test Analyst”

Reply

Mark

 While the general content is fine, as a BI professional I would strongly recommend avoiding the
use of 3D pie charts to present data.

Reply

Promode

Very Informative, However things like “list of knows” , “Test bed” information links etc are
missing.

Reply

peoplesoft hrms functional online training

nice post thanks for sharing this post.

Reply

El

There is still an issue with downloading the sample test report summary.

Reply

el

February 2021. Issue still there.

Reply

Leave a Comment

Name *

Email *

POST COMMENT

About SoftwareTestingHelp

Helping our community since 2006!

Most popular portal for Software professionals with 100
million+ visits and 300,000+ followers! You will absolutely love our tutorials on QA Testing,
Development, Software Tools and Services Reviews and more!

Recommended Reading

How to Write Software Testing Weekly Status Report

Sample Template for Acceptance Test Report with Examples
How to Report Test Execution Smartly – [Download Status Report Template]
Sample Test Case Template with Test Case Examples [Download]
Software Testing Documentation Guide (Why It’s Important)
How to Write a Good Bug Report? Tips and Tricks

6 Most Important Steps to Make Your Test Reports Even Better
How To Write Test Strategy Document (With Sample Test Strategy Template)

JOIN Our Team!

ABOUT US | CONTACT US | ADVERTISE

ALL ARTICLES ARE COPYRIGHTED AND CANNOT BE REPRODUCED WITHOUT PERMISSION.

© COPYRIGHT SOFTWARETESTINGHELP 2021 — READ OUR COPYRIGHT POLICY | PRIVACY POLICY | TERMS | COOKIE POLICY |
AFFILIATE DISCLAIMER