This test closure report can be used a sample report for all agile based projects. We can send this report on closure of our testing at the end of Sprint or for any release.
Testing Closure Report
<Project/Product Name>
(Test Cycle/Iteration#)
Overview
This document provides us a summary of the testing conducted and the status of the release in terms of bugs and requirements coverage. These testing activities include all layers of testing conducted throughout testing life cycle i.e. Agile/Component Level QA, End-End QA, UAT etc. he
Project/Product Name | ||||||||||||||
Sprint Number | ||||||||||||||
Test Cycle/Iteration Number | ||||||||||||||
QA POC | ||||||||||||||
QA Manager/Reviewer | ||||||||||||||
Product Development Manager | ||||||||||||||
Development Lead | ||||||||||||||
Total Bug(s) | Blocker | Critical | Major | Minor | Trivial | |||||||||
Testing Stages/Levels/Types Covered | Component/Functional Level Testing: | |||||||||||||
System/Integration, End-End Testing | ||||||||||||||
UAT | ||||||||||||||
Post deployment testing | ||||||||||||||
Regression Testing | ||||||||||||||
Security Testing | ||||||||||||||
Test Cases Summary | Passed | 27 | Failed | Inconclusive | 00 | |||||||||
User Stories In Test Scope | No, of Stories Tested | User Story ID’s | ||||||||||||
Definitions
• QA: Quality Assurance
• POC: Point of Contact
• UAT: User Acceptance Testing N/A: Not Applicable (If any section is not required in reporting it will be marked as Not applicable)
Bug Status Description
Status | Description |
Open | Newly created bugs. |
Confirmed/ Reopened | Bugs which are re-opened by QA after verification of the fixes provided by Dev. |
In Progress | Bugs on which development is currently working. |
UNDER QA/REVIEW (STG) / Resolved | Bugs which are fixed by the development and need verification by QA |
Verified | Bugs which are fixed by development and verified by QA |
VERIFIED/STG | Bugs which are fixed by development and verified by QA on Staging environment |
VERIFIED/PRD | Bugs which are verified on production |
NOT AN ISSUE | Bug’s which are not valid either requirements were changed after bug was reported or its not accordingly to requirements |
Closed | All verified bugs |
Bug Severity Description
Severity | Description |
Blocker | Software does not run at all; complete failure of the primary product feature and does not have a workaround; issues declared as “blockers” by client. |
Critical | Customer experience is severely impacted across the product |
Major | Significant part of product does not work, product crashes in obscure cases; no obvious workaround. |
Minor | Minor part or feature of product does not work |
Trivial | Design, cosmetic and text issues |
Release/Build & Test Environment Details
Build/Release Information’s
Build | Version/URL |
IOS | |
Android | |
Web |
Test Environment Details
Web | |
Browser/Device | Version |
Firefox | |
Internet Explorer | |
Chrome | |
IOS | |
Device | OS |
Android | |
Device | OS |
Test Coverage
Sprint no. | No, of Stories Tested | Tested User Stories ID’s | User Stories ID’s Not is Scope |
Test Summary
Test Levels/Stages covered
Specify the testing stage for this Test Summary Report.
Testing Stage | Status |
Component/Functional Level Testing | |
System/Integration, End-End Testing | |
UAT | |
Production Sanity Testing | |
Performance Testing | |
Regression Testing |
Test Case Summary
Test Cycle# | No. of Planned Test Cases | No. of Executed Test Cases | Passed | Failed | Inconclusive |
Bugs Summary
Report Summary | Blocker | Critical | Major | Minor | Trivial | Total | % |
Open | 00 | 00 | 00 | 00 | 00 | 00 | 0 |
In Progress | 00 | 00 | 00 | 00 | 00 | 00 | 0 |
Reopened | 00 | 00 | 00 | 00 | 00 | 00 | 0 |
UNDER QA/REVIEW (STG) | 00 | 00 | 00 | 00 | 00 | 00 | 0 |
VERIFIED/STG | 00 | 00 | 00 | 00 | 00 | 00 | 0 |
VERIFIED/PRD | 00 | 00 | 00 | 00 | 00 | 00 | 0 |
NOT AN ISSUE | 00 | 00 | 00 | 00 | 00 | 00 | 0 |
Closed | 00 | 00 | 00 | 00 | 00 | 00 | 0 |
Total | 00 | 00 | 00 | 00 | 00 | 00 |
Major Open Bugs Summary
Total Open Bug’s | ||||||
ID | Severity | Type | ||||
Summary | ||||||
Probability of Occurrence | No, of executed tests: | |||||
No, of occurrence: | ||||||
Occurrence Probability: | ||||||
ID | Severity | Type | ||||
Summary | ||||||
Probability of Occurrence | No, of executed tests: | |||||
No, of occurrence: | ||||||
Occurrence Probability: | ||||||
ID | Severity | Type | ||||
Summary | ||||||
Probability of Occurrence | No, of executed tests: | |||||
No, of occurrence: | ||||||
Occurrence Probability: | ||||||
ID | Severity | Type | ||||
Summary | ||||||
Probability of Occurrence | No, of executed tests: | |||||
No, of occurrence: | ||||||
Occurrence Probability: | ||||||
ID | Severity | Type | ||||
Summary | ||||||
Probability of Occurrence | No, of executed tests: | |||||
No, of occurrence: | ||||||
Occurrence Probability: | ||||||
Reference Documents
Document Description | Attachment |
Testing Check list | |
Test Cases Document | |
All Bugs detailed report |
Recommendation
QA Notes:
Sr. no | Notes |
1 | |
2 | |
3 | |
4 | |
5 | |
6 | |
7 |
Improvement Areas Observed:
Sr. no | Notes |
1 | |
2 | |
3 | |
4 | |
5 | |
6 | |
7 |
Conclusion:
“Release is stable”
“Release is not stable”
Post a Comment