Test Report

<Project or Solution Name>

U.S. Department of Housing and Urban Development

<Month, Year>

Test Report

Solution Information
Information
Solution Name Solution Acronym Project Cost Accounting System (PCAS) Identifier Document Owner Project Sponsor Version/Release Number <Solution Name> <Solution Acronym> <PCAS Identifier> <Owner Name> <Sponsor Name> <Version/Release Number>

Document History
<Provide information on how the development and distribution of the Test Report is controlled and tracked. Use the table below to provide the version number, date, author, and a brief description of the reason for creating the revised version.> Version No. Date Author Revision Description

Note to the Author

The control gate criteria for each of the seven phases of the Department of Housing and Urban Developments (HUD) Project Planning and Management (PPM) Life Cycle require the completion of various artifacts. Each information technology (IT) project, working in conjunction with the Office of the Chief Information Officer (OCIO), will capture decisions around the PPM Life Cycle tailoring in the Project Process Agreement (PPA), which documents the reasons for using, combining or skipping specific artifacts applicable to the project. This document is a template for a Test Report that is to be completed during the Execution of Solution Phase, the fourth phase of the PPM Life Cycle. The template includes instructions to the author, boilerplate text, and fields that should be replaced with the values specific to the project: Blue italicized text enclosed in angle brackets (<text>) provides instructions to the document author or indicates a field that should be replaced with information specific to a particular project. Text and tables in black are provided as boilerplate examples of wording and formats that may be used or modified as appropriate to a specific project. These are offered only as suggestions to assist in developing project documents; they are not mandatory formats.
Page i

Version 1.1 6/9/2011

Test Report

Test Report Authorization Memorandum

I have carefully assessed the Test Report for <Project Name>. This document has been completed in accordance with the requirements of the HUD PPM Life Cycle. MANAGEMENT CERTIFICATION - Please check the appropriate statement. ______ The document is accepted. ______ The document is accepted pending the changes noted. ______ The document is not accepted. We fully accept the content within this project artifact and associated tasks.
_____________________ _________ ________________ _____

NAME Business Project Manager ______________________________ NAME Project Sponsor _______________________________ NAME Technical Review Sub-Committee _______________________________ NAME Investment Review Sub-Committee (if applicable) _______________________________ NAME Customer Care Committee (if applicable) _______________________________ NAME Executive Investment Board (if applicable)

DATE

_____________________ DATE

_____________________ DATE

_____________________ DATE

_____________________ DATE

_____________________ DATE

Version 1.1 6/9/2011

Page ii

Test Report

Content
1. 2. 3. Purpose ................................................................................................................................................ 1 Test Summary....................................................................................................................................... 2 Test Results .......................................................................................................................................... 3 3.1 3.2 4. 5. Solution/Integration Testing ......................................................................................................... 3 User Acceptance Testing ............................................................................................................... 3

Variances .............................................................................................................................................. 4 Summary of Defects ............................................................................................................................. 5 5.1 5.2 Open Defects................................................................................................................................. 5 Closed Defects............................................................................................................................... 6

6.

Recommendations ............................................................................................................................... 7

Appendix A: References ................................................................................................................................ 8 Appendix B: Key Terms ................................................................................................................................. 9

Version 1.1 6/9/2011

Page iii

Test Report

1. Purpose
The Test Report documents the results of the solution, integration, user acceptance, and security tests conducted for the <Project Name>. The Test Report records the results of the tests, presents the deficiencies for review, and provides a means of assessing software progression to the next stage of testing or readiness for deployment to production. This document provides a basis for assigning responsibility for deficiency correction and follow up, and for preparation of a statement of project completion. The intended audience for the Test Report is the integrated project team (IPT) members and any other stakeholders responsible for reviewing the test results, addressing deficiencies, and/or assessing the systems readiness for deployment to the production environment.

Version 1.1 6/9/2011

Page 1

Test Report

2. Test Summary
<Provide high level measurements regarding the testing activities executed for the solution. If the project team uses a repository such as Quality Center to track the status of test cases and defects, table below may be replaced with information extracted from the repository.> Category Number of Test Cases Planned Number of Test Cases Executed Number of Number of Number Number Number Number Test Cases Test Cases of of Fatal of of Executed Executed Resolved Defects Major Minor Successfully Unsuccessfully Defects Defects Defects

Total Table 1 - Sample Test Summary Report

Suggested Severity Legend: Minor: A defect that will not cause a failure in execution of the product Major: A defect that will cause an observable product failure or departure from requirements Fatal: A defect that will cause the system to crash or close abruptly or affect other applications

Version 1.1 6/9/2011

Page 2

Test Report

3. Test Results
<Summarize the test results that were within the scope of the Test Plan. Include a detailed description of any deviations from the original test plan, design, test case, or expected results. Include any issues or bugs discovered during the test. If the project team uses a repository such as Quality Center to track the status of test cases and defects, the tables below may be replaced with information extracted from the repository. If necessary, add other subsections to record the results of other categories of testing.>

3.1 Solution/Integration Testing

Table 2 below summarizes the results of solution/integration testing: Test Case ID Date Tested Tester Pass/Fail Severity of Defect Summary of Defect Comments Test Incident ID

Table 2 - Sample System/Integration Testing Summary Report

3.2 User Acceptance Testing

Table 3 below summarizes the results of user acceptance testing: Test Case ID Date Tested Tester Pass/Fail Severity of Defect Summary of Defect Comments Test Incident ID

Table 3 - Sample User Acceptance Testing Summary Report

Version 1.1 6/9/2011

Page 3

Test Report

4. Variances
<Describe any variances between the planned testing and the actual testing. Also, provide an assessment of the manner in which the test environment may be different from the operational environment and the effect of this difference on the test results.>

Version 1.1 6/9/2011

Page 4

Test Report

5. Summary of Defects
5.1 Open Defects
<The defect log can be generated from any HUD-standard defect-tracking tool such as Quality Center.> Severity
1 2 3 4 Urgent High Medium Low 1 2 3 4

Priority
Critical High Moderate Low

ID#

Source
<Provide the associated test case ID number>

Bug/Defect Description
<Describe the bug/defect. Include error message generated, sequence of events that triggered it, etc.>

Severity
<Refer to Severity/ Priority charts>

Priority
<Refer to Severity/ Priority charts>

Resolution Strategy
<Identify what steps need to be taken, and by whom, to resolve the identified problem>

Associated Change Request

<If applicable, enter a change request number associated with correcting this bug/ defect>

Table 4 Sample Summary of Open Defects

Version 1.1 6/9/2011

Page 5

Test Report

5.2 Closed Defects

<The defect log can be generated from any HUD-standard defect-tracking tool such as Quality Center.> Severity
1 2 3 4 Urgent High Medium Low 1 2 3 4

Priority
Critical High Moderate Low

ID#

Source

Bug/Defect Description

Severity

Priority

Resolution Strategy
<Identify what steps were taken, and by whom, to resolve the identified problem>

Associated Change Request

<If applicable, enter a change request number associated with correcting this bug/ defect>

Date Resolved
<Enter the date when the issue was resolved>

<Provide the associated test case ID number>

<Describe the bug/defect. Include error message generated, sequence of events that triggered it, etc.>

<Refer to Severity/ Priority charts>

<Refer to Severity/ Priority charts>

Table 5 Sample Summary of Closed Defects

Version 1.1 6/9/2011

Page 6

Test Report

6. Recommendations
<Provide any recommended improvements in the design, operation, or future testing of the solution that resulted from the test activities. Provide a discussion of each recommendation and its impact on the business product. If there are no recommendations to report, simply state that fact.>

Version 1.1 6/9/2011

Page 7

Test Report

Appendix A: References
<Insert the name, version number, description, and physical location of any documents referenced in this document. Add rows to the table as necessary.> Table 6 below summarizes the documents referenced in this document. Document Name
<Document name and version number>

Description
<Document description>

Location
<URL to where document is located>

Table 6 - References

Version 1.1 6/9/2011

Page 8

Test Report

Appendix B: Key Terms

Table 7 below provides definitions and explanations for terms and acronyms relevant to the content presented within this document. Term
[Insert Term]

Definition
<Provide definition of term and acronyms used in this document>

Table 7 - Key Terms

Version 1.1 6/9/2011

Page 9