1. Test Closure Report:
Test Closure report is a report that is created once the testing phase is successfully
completed by meeting exit criteria defined for the project.
Test Closure is created by Test Lead, reviewed by various stake holders like Test architect,
Test manager, Business Analyst, Project manager and finally approved by clients.
Test Closure memo contains details of the test passes carried out, results of each pass,
outstanding defects and how they would be dealt with once the post production goes live
etc.
What are test closure documents?
In my company, a Test Closure Document contains a checklist of all of the items that must
be met in order to close a test project as well as a list of activities that must be performed
after the project is closed. This document may include (not an exhaustive list):
BEFORE CLOSING A TEST PROJECT
1) Exit criteria is met
2) Testing performed against test plan
3) All test cases are mapped to requirements
4) All test cases have been executed unless known and agreed upon
5) All defects addressed
AFTER CLOSING A TEST PROJECT
1) Highlights and lowlights
2) Lessons learned
3) Process improvements
4) Test estimation evaluation
5) Defect trend analysis
6) Properly archive all relevant test collateral
- test plan(s)
- test report(s)
- test data
- Relevant emails

2. In contrast, a Test Closure Report is typically a simple email sent to all relevant stake
holders which indicates that testing is complete and QA either approves or disapproves the
release of the application based on whether or not it had met the company's exit criteria.
This report provides details which substantiate the "Go / No-Go" decision such as:
- # defects found
- # defects fixed
- # open total defects
- # open by Severity and Priority
- # postponed defects
- # not-run test cases
- # blocked test cases
- Items of concern