Test Summary Report

Total Page:16

File Type:pdf, Size:1020Kb

Test Summary Report

TEST REPORT

for

Project Name (Project Acronym) #.# [do not put the word version]

Prepared for : United States Patent and Trademark Office Office of the Chief Information Officer

Prepared on Month Day, Year

Approved by :

OCIO Project System Development Lead Business Project Manager Manager

Date Date Date Project Name Test Report

ii Month DD, YYYY/version Project Name Test Report

TABLE OF CONTENTS

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

2 VARIANCES...... 2-1 2.1 Variances and Explanations...... 2-1

3 RESULTS...... 3-1 3.1 Discrepancy Reports...... 3-1 3.2 Test Observation Reports...... 3-1 3.3 Open Issues...... 3-1

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

i Month DD, YYYY/v.1 Project Name Test Report

1 SUMMARY

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

[Project name and version] met all requirements as defined in the RTMx Report (RTMx) [or Use Cases], created on [MM/DD/YYYY].

1.1 System Tested

1.2 Dates of Testing

FQT was performed on MMDDYYYY or from MMDDYYYY through MMDDYYYY.

1.3 Test Environment

1.3.1 Hardware

1.3.1.1 Workstation Hardware Workstation Hardware Workstation 1 Component A Component B Workstation 2 Component A Component B

1.3.1.2 Server Hardware Server Hardware Server 1 Component A Component B Server 2 Component A Component B

1.3.2 Software

1.3.2.1 Workstation Software Workstation Software Workstation 1 Component A

1 Month DD, YYYY/v.1 Project Name Test Report

Component B Workstation 2 Component A Component B

1.3.2.2 Server Software Server Software Server 1 Component A Component B Server 2 Component A Component B

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].

2 Month DD, YYYY/v.1 Project Name Test Report

2 VARIANCES

2.1 Variances and Explanations

[Put text here.]

1 Month DD, YYYY/v.1 Project Name Test Report

3 RESULTS

3.1 Discrepancy Reports

There were [state the #] of DRs identified.

Critical Major Minor Total Open # # # # Closed # # # # Deferred # # # # Totals # # # #

Appendix D contains a detailed list of DRs.

3.2 Test Observation Reports

There were [state the #] TORs identified.

Appendix E contains a detailed list of the TORs.

3.3 Open Issues

[Put text here.]

1 Month DD, YYYY/v.1 Project Name Test Report

4 ACTIVITIES

4.1 Methodology

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.

4.2 Staffing

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].

4.3 Testing Staff Access to System

[Put text here.]

4.4 Builds Tested

[Put text here. FQT was performed on [one or multiple (#)] Configuration Management (CM) build[s].

Build # Test Cases 1 2 3 4 5

1 Month DD, YYYY/v.1 Project Name Test Report

APPENDIX A ACRONYMS AND ABBREVIATIONS

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

1 Month DD, YYYY/v.1 Project Name Test Report

APPENDIX B REFERENCED DOCUMENTS

The following documents are either referenced in or were used in preparation of this document:

Formal Qualification Testing Specifications and Procedures for [Project Name], Month DD, YYYY.

Test Plan for [Project Name].

RTMx [or Use Cases] [for Project Name, Month DD, YYYY].

1 Month DD, YYYY/v.1 Project Name Test Report

APPENDIX C TEST CASE DESCRIPTIONS

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

1 Month DD, YYYY/v.1 Project Name Test Report

APPENDIX D DETAILED DISCREPANCY REPORT

1 Month DD, YYYY/v.1 Project Name Test Report

APPENDIX E DETAILED TEST OBSERVATION REPORT

1 Month DD, YYYY/v.1

Recommended publications