TESTING

Big picture with Test Summary Report

October 17th, 2017 No Comments

Test summary report is a formal document summarizes the results of all testing efforts for a testing cycle of a project / module or a sub module. Generally, Sr Testers, test leads or test managers prepare this document at the end of testing cycle. The objective of this report is:

  • Summarize all the testing that was performed since the previous test summary report.
  • Enable project management and the customer to know the status of project testing.

 

Why test Summary report is important?

 

  • It will justify the testing effort that testing team has put in the project.
  • It will help in building more mature process
  • Project management and the customer are informed of the status of project testing.
  • Project management and the customer are informed of the status of application quality.
  • Project management and the customer can take corrective action if necessary.

 

When to make:

 

This report should be created and published after every test run cycle.

This report should contain information about What is completed in terms of testing, development, Bugs information and any known issues to be shared with customer.

The ideal situation is to make this report in form of metric, charts or tables. So that it gives the information at a glance.

Test summary report Template:

 

Please zoom your browser window to have clear picture of table content.

Here is the format which we follow during our QA process:

Introduction:

Report name: Mention the type of Report

Date: Date when report is created

Project: Name of Project/Application

Iteration Number: Mention the Iteration number

QA: Who was the QA resource for this project

Table content:

Req ID/User ID: Mention the Requirement ID or user ID

Req/User story Title: In this we mention the module name or the Short Req Name

Dev Update: We have created this as additional column to give complete picture of the project. In this we mention the status of that requirement from development perspective.

Developer name: Who worked on that requirement.

Test scenario/Test cases details:

  • Number of test cases planned.
  • Number or percentage of test cases implemented.
  • Number or percentage of test cases executed.
  • Number or percentage of test cases passed.
  • Number or percentage of test cases failed (total and by priority).
  • Status of Testing for that user story or Requirement.

 

Defect Information:

  • Total open bugs
  • New bugs found by priorities.
  • Total count of Reopened bugs against requirement/user story.

 

This table will also be represented in Graph,to provide better view and clear picture.

This report will also have additional two sheets which contains details of Open bugs and other sheet with List of Known issues. It can be created or exported from tool (In our case we use Jira).It might be difficult to prepare this report when we deal with short time projects.


Tags:

About the author

User Acceptance Testing

No Comments

TeamSTAR 2017- The Magic of Testing Meetup in INDIA

No Comments

Similarity between Kids and Testing

2 Comments

Obligatory and first document in Software testing life cycle

No Comments

STWC, Results – Sixer in Software Testing World Cup ASIA- 2016

No Comments

STWC-Software testing world cup-ASIA,2016 – The Beginning

3 Comments

Your email address will not be published. Required fields are marked *