<p> TEST REPORT</p><p> for </p><p>Project Name (Project Acronym) #.# [do not put the word version]</p><p>Prepared for : United States Patent and Trademark Office Office of the Chief Information Officer</p><p>Prepared on Month Day, Year</p><p>Approved by :</p><p>OCIO Project System Development Lead Business Project Manager Manager</p><p>Date Date Date Project Name Test Report</p><p> ii Month DD, YYYY/version Project Name Test Report</p><p>TABLE OF CONTENTS</p><p>1 SUMMARY...... 1-1 1.1 System Tested...... 1-1 1.2 Dates of Testing...... 1-1 1.3 Test Environment...... 1-1 1.3.1 Hardware...... 1-1 1.3.2 Software...... 1-1 1.3.3 Other Needs...... 1-2</p><p>2 VARIANCES...... 2-1 2.1 Variances and Explanations...... 2-1</p><p>3 RESULTS...... 3-1 3.1 Discrepancy Reports...... 3-1 3.2 Test Observation Reports...... 3-1 3.3 Open Issues...... 3-1</p><p>4 ACTIVITIES...... 4-1 4.1 Methodology...... 4-1 4.2 Staffing...... 4-1 4.3 Testing Staff Access to System...... 4-1 4.4 Builds Tested...... 4-1 APPENDIX A ACRONYMS AND ABBREVIATIONS...... A-1 APPENDIX B REFERENCED DOCUMENTS...... B-1 APPENDIX C TEST CASE DESCRIPTIONS...... C-1 APPENDIX D DETAILED DISCREPANCY REPORT...... D-1 APPENDIX E DETAILED TEST OBSERVATION REPORT...... E-1</p><p> i Month DD, YYYY/v.1 Project Name Test Report</p><p>1 SUMMARY</p><p>There were [#] Discrepancy Reports (DRs) and [#] Test Observation Reports (TORs) identified during Formal Qualification Testing (FQT). [#] were eventually closed, [#] were deferred, and [#] remain open. or</p><p>[Project name and version] met all requirements as defined in the RTMx Report (RTMx) [or Use Cases], created on [MM/DD/YYYY].</p><p>1.1 System Tested</p><p>1.2 Dates of Testing</p><p>FQT was performed on MMDDYYYY or from MMDDYYYY through MMDDYYYY.</p><p>1.3 Test Environment</p><p>1.3.1 Hardware</p><p>1.3.1.1 Workstation Hardware Workstation Hardware Workstation 1 Component A Component B Workstation 2 Component A Component B</p><p>1.3.1.2 Server Hardware Server Hardware Server 1 Component A Component B Server 2 Component A Component B</p><p>1.3.2 Software</p><p>1.3.2.1 Workstation Software Workstation Software Workstation 1 Component A</p><p>1 Month DD, YYYY/v.1 Project Name Test Report</p><p>Component B Workstation 2 Component A Component B</p><p>1.3.2.2 Server Software Server Software Server 1 Component A Component B Server 2 Component A Component B</p><p>1.3.3 Other Needs a) User accounts with user identifications (IDs) and passwords authorized for required functions. b) Network components. c) [Interface System name]. d) [Interface System name].</p><p>2 Month DD, YYYY/v.1 Project Name Test Report</p><p>2 VARIANCES</p><p>2.1 Variances and Explanations</p><p>[Put text here.]</p><p>1 Month DD, YYYY/v.1 Project Name Test Report</p><p>3 RESULTS</p><p>3.1 Discrepancy Reports</p><p>There were [state the #] of DRs identified.</p><p>Critical Major Minor Total Open # # # # Closed # # # # Deferred # # # # Totals # # # #</p><p>Appendix D contains a detailed list of DRs.</p><p>3.2 Test Observation Reports</p><p>There were [state the #] TORs identified.</p><p>Appendix E contains a detailed list of the TORs.</p><p>3.3 Open Issues</p><p>[Put text here.]</p><p>1 Month DD, YYYY/v.1 Project Name Test Report</p><p>4 ACTIVITIES</p><p>4.1 Methodology</p><p>The testing staff used the RTMx [or Use Cases], created on [MM/DD/YYYY], as a basis for writing the Formal Qualification Testing Specifications and Procedures [or Formal Qualification Testing Scenarios and Procedures if using Use Cases]. The test procedures provided the initial conditions, operator actions, and expected results needed to verify the requirements during FQT. There were [#] test cases covering [#] requirements (see Appendix C). The testing staff recorded and tracked DRs and TORs in TestDirector.</p><p>4.2 Staffing</p><p>SRA International, Inc. (SRA) staff performed the FQT. The [System Development Manager], [Name], the [OCIO Project Manager], [Name], and the Pre-Production Services Division (PPSD)/ Information Technology Testing Branch (ITTB) [Test Manager], [Name] witnessed the FQT. [Name] provided [special assistance].</p><p>4.3 Testing Staff Access to System</p><p>[Put text here.]</p><p>4.4 Builds Tested</p><p>[Put text here. FQT was performed on [one or multiple (#)] Configuration Management (CM) build[s].</p><p>Build # Test Cases 1 2 3 4 5</p><p>1 Month DD, YYYY/v.1 Project Name Test Report</p><p>APPENDIX A ACRONYMS AND ABBREVIATIONS</p><p>CM Configuration Management DR Discrepancy Report FQT Formal Qualification Testing HP Hewlett-Packard ID Identification ITTB Information Technology Testing Branch NT New Technology PPSD Pre-Production Services Division PTOnet USPTO's campus-wide network RTMx RTMx Report SRA SRA International, Inc. TOR Test Observation Report WS Workstation</p><p>1 Month DD, YYYY/v.1 Project Name Test Report</p><p>APPENDIX B REFERENCED DOCUMENTS</p><p>The following documents are either referenced in or were used in preparation of this document:</p><p>Formal Qualification Testing Specifications and Procedures for [Project Name], Month DD, YYYY.</p><p>Test Plan for [Project Name].</p><p>RTMx [or Use Cases] [for Project Name, Month DD, YYYY].</p><p>1 Month DD, YYYY/v.1 Project Name Test Report</p><p>APPENDIX C TEST CASE DESCRIPTIONS</p><p>Test Case Test Case Description Requirement No. Test Case 1 – This test case will show that only TEAS 1.1-4, TEAS 1.1-5 Security authorized users can access the system</p><p>1 Month DD, YYYY/v.1 Project Name Test Report</p><p>APPENDIX D DETAILED DISCREPANCY REPORT</p><p>1 Month DD, YYYY/v.1 Project Name Test Report</p><p>APPENDIX E DETAILED TEST OBSERVATION REPORT</p><p>1 Month DD, YYYY/v.1 </p>