Project Name
Document Version 1.0
Prepared by Jane Doe, ITS
Last Edited July 28, 2017
PLAN
REQUIREMENTS
SOLUTION
ANALYSIS
DESIGN
BUILD
TEST
TRAIN/DEPLOY MAINTENANCE
TO THE DOCUMENT OWNER: This template is provided as a guideline and resource. The structure and instructions
give detail about what might go into a completed document. Only you and your team, however, know what will
best fit the needs of your specific effort, and you are encouraged to adapt the template as appropriate to meet
those needs.
Test Closure Memo
The Test Closure Memo summarizes the tests performed during the project. This template may be used
both for interim test reporting at the end of a phase and for final test reporting at the end of the project.
The document should provide a summary of the state of the system for stakeholders, especially if
provided prior to a Go/No-Go decision. Any issues or weaknesses with the product that were uncovered
as a result of the testing should be included, as well as a discussion of how these will be handled and
could affect the product. Please reference the Go Live Checklist for detailed requirements of activities and
documentation needed prior to the release of the application or system to ensure all were addressed
during the test phase. If there are defects to be resolved at a later date or if there is a phased rollout,
explain any functionality that is not available and/or the workarounds.
The audiences for this report are as follows:
 Director -- Reviews for test completeness and alarms
 Project Manager – Approves for completeness, identifies potential communication points
 Build Team – Reviews for completeness
 Training Team – Reviews for alarms, identifying potential training points
 Customer Steering Committee – Approves prior to deployment
Executive Summary
Describe the purpose of the testing and summarize the results. Provide a general statement of the
capability of the system as demonstrated by the testing, compared with the requirements and design.
Summarize the major functions tested and the results. Address any issues or weaknesses of major
priority or higher that have not been remediated in the chart below.
Page 1 of 5
Project Name
Document Version 1.0
Remaining Major Issues
Jira issue # and description
Plan/Workaround
All minor and trivial issues will be moved to the sustainment backlog.
Test Analysis
Security Considerations
Provide a detailed description of the security requirements that have been built into the system and
verified during system acceptance testing. Identify and describe security issues or weaknesses that were
discovered as a result of testing. If testing was completed by members of the Information Security Office
(ISO), detail findings and associated fixes.
Functional Testing
Include a brief description of the functional testing as described in the functional test plan. Describe any
deviations from the original test plan that occurred during performance of the test and list reasons for
the deviations.
Describe the expected outcome and the actual outcome for the functional testing that was performed.
Non-functional Testing
Include a brief description of the non-functional testing as described in the non-functional test plan.
Describe any deviations from the original test plan that occurred during performance of the test and list
reasons for the deviations.
Describe the expected outcome and the actual outcome for the non-functional testing that was
performed.
User Acceptance Testing
Include a brief description of the user acceptance testing as described in the test plan. Describe any
deviations from the original test plan that occurred during performance of the test and list reasons for
the deviations.
Describe the expected outcome and the actual outcome for the user acceptance testing that was
performed.
Test Closure Memo
Page 2 of 5
Project Name
Document Version 1.0
Accessibility Testing
Include a brief description of the results of accessibility testing. Describe any findings and associated
fixes.
Describe the expected outcome and the actual outcome for the accessibility testing that was performed.
Summary and Recommendations
There are different types of tests that are used to validate that software performs the intended function
with the anticipated features. Document any requirements not met. Also document any exit criteria for
specific test types that were not met. Include overall test results for each type in the chart below.
Test Type
% test cases
executed
% test cases
passed
Test phase
Notes: clarify any situations in which
completion date test cases could not be executed
Functional/Component
System & Integration
Recovery & Error Handling
Accessibilty
Performance
Load and Stress
Security
User Acceptance
Final Regression
Remaining Issues
Indicate the number of defects remaining by priority.
Test Closure Memo
Page 3 of 5
Project Name
Document Version 1.0
Remaining Issues
Blocker
Critical
Major
Minor
Trivial
Total
Deficiencies
What deficiencies were discovered during testing? If the deficiency has not been corrected, list the
consequences to the project/product. If the deficiency has been corrected, note that.
Recommended Improvements
Provide a detailed description of any recommendations discovered during testing that could improve the
system, its performance, or its related procedures. If additional functionality is seen as a potential
improvement for the user, it should be included here. Provide a priority ranking of each recommended
improvement relative to all suggested improvements for the system.
System Acceptance
Summarize how testing has shown that the system is ready for release testing and subsequent
production operation.
Next Steps
Describe how issues will be addressed in the near feature. If appropriate, insert a summary of
outstanding issues from JIRA or any other defect tracking software.
Revision History
Identify document changes.
Version
Date
Updater Name
v 1.0
Description
Initial draft completed.
Signatures
Formal written signoff is preferred for larger, more complex projects.
Name
Test Closure Memo
Role
Signature
Date
Page 4 of 5
Project Name
Document Version 1.0
Test Closure Memo
Page 5 of 5