EPLC_System_Test_Report_r . _v . .doc

SUBJECT \* MERGEFORMAT System Test Report

Version: <1.0> Error! Unknown document property name.

Food and Drug Administration

<Project Name & Release Version #> Enterprise Performance LifeCycle

SYSTEM TEST REPORT

Document Version Number: <1.0> Document Version Date: <mm/dd/yyyy> Notes to the Author

[This document is a template of a System Test Report document for a project. 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 square brackets ([text]) provides instructions to the document author, or describes the intent, assumptions and context for content included in this document.

· Blue italicized text enclosed in angle brackets (<text>) 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.

When using this template for your project document, it is recommended that you follow these steps:

1. Replace all text enclosed in angle brackets (e.g., <Project Name>) with the correct field values. These angle brackets appear in both the body of the document and in headers and footers. To customize fields in Microsoft Word (which display a gray background when selected):

a. Select File>Properties>Summary and fill in the Title field with the Document Name and the Subject field with the Project Name.

b. Select File>Properties>Custom and fill in the Last Modified, Status, and Version fields with the appropriate information for this document.

c. After you click OK to close the dialog box, update the fields throughout the document with these values by selecting Edit>Select All (or Ctrl-A) and pressing F9. Or you can update an individual field by clicking on it and pressing F9. This must be done separately for Headers and Footers.

2. Modify boilerplate text as appropriate to the specific project.

3. To add any new sections to the document, ensure that the appropriate header and body text styles are maintained. Styles used for the Section Headings are Heading 1, Heading 2 and Heading 3. Style used for boilerplate text is Body Text.

4. To update the Table of Contents, right-click and select “Update field” and choose the option- “Update entire table”

5. Before submission of the first draft of this document, delete this “Notes to the Author” page and all instructions to the author, which appear throughout the document as blue italicized text enclosed in square brackets.]

VERSION HISTORY

[Provide information on how the development and distribution of the System Test Report was controlled and tracked. Use the table below to provide the version number, the author implementing the version, the date of the version, the name of the person approving the version, the date that particular version was approved, and a brief description of the reason for creating the revised version.]

By Revision

Date Approved

By Approval

Date Description of and

Reason for

Change

Table of Contents 51.0 Introduction

51.1 Purpose

52.0 Test Summary

52.1

TEST TYPE (FUNCTION, UNIT, SYSTEM, ETC.)

52.2

52.3

63.0 Test Assessment

74.0 Test Results

74.1

UNIT / MODULE / SYSTEM / TESTING

74.2

SYSTEM TESTING

74.3

USER ACCEPTANCE TESTING

84.4

AD HOC TESTING

84.5

REGRESSION TESTING

94.6

PERFORMANCE TESTING

94.7

<TYPE OF TEST>

115.0 Variances

116.0 Test Instances

116.1

RESOLVED IN TEST INCIDENTS

116.2

UNRESOLVED IN TEST INCIDENTS

117.0 Recommendations

12APPENDIX A: SYSTEM TEST REPORT APPROVAL

13APPENDIX B: REFERENCES

14APPENDIX C: KEY TERMS

1.0 Introduction

1.1 Purpose

This <Project Name> Test Report provides a summary of the results of test performed as outlined within this document.

2.0 Test Summary

[Include basic information about what was tested and what happened.]

Project Name: [Project name] System Name: [System name] Version Number: [Version number] Additional Comments: [Enter any additional comments]

2.1 TEST TYPE (FUNCTION, UNIT, SYSTEM, ETC.)

[Include basic information about what was tested and what happened.]

Test Owner: [John Doe] Test Date: [mm/dd/yyyy] - [mm/dd/yyyy] Test Results: [Enter a summary of the test conducted and results] Additional Comments: [Enter any summary comments]

2.2 TEST TYPE (FUNCTION, UNIT, SYSTEM, ETC.)

[Include basic information about what was tested and what happened.]

Test Owner: [John Doe] Test Date: [mm/dd/yyyy] - [mm/dd/yyyy] Test Results: [Enter a summary of the test conducted and results] Additional Comments: [Enter any summary comments]

2.3 TEST TYPE (FUNCTION, UNIT, SYSTEM, ETC.)

[Include basic information about what was tested and what happened.]

Test Owner: [John Doe] Test Date: [mm/dd/yyyy] - [mm/dd/yyyy] Test Results: [Enter a summary of the test conducted and results] Additional Comments: [Enter any summary comments]

3.0 Test Assessment

[Enter a comprehensive assessment of your interpretation of how adequate the test was in light of how thorough the test plan said it should be? What wasn't tested well enough?]

4.0 Test Results

[Summarize the test results. 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.]

4.1 TC "\"5.A. CMS Employees and Users of CMS IT Resources\"" \l 2 UNIT / MODULE / SYSTEM / TESTING Unit, module, and system integration testing activities were performed during the development of the system build or release.

4.2 TC "\"5.A. CMS Employees and Users of CMS IT Resources\"" \l 2 SYSTEM TESTING The table below summarizes the results of system testing:

<Yes> or <No>

[If the test case failed, list the corresponding Test Incident ID in the Comments column.]

4.3 TC "\"5.A. CMS Employees and Users of CMS IT Resources\"" \l 2 USER ACCEPTANCE TESTING The table below summarizes the test cases employed for user acceptance testing and the test results obtained for each test case:

<Yes> or <No>

4.4 TC "\"5.A. CMS Employees and Users of CMS IT Resources\"" \l 2 AD HOC TESTING The table below summarizes the test cases employed for ad hoc testing and the test results obtained for each test case:

<Yes> or <No>

4.5 TC "\"5.A. CMS Employees and Users of CMS IT Resources\"" \l 2 REGRESSION TESTING The table below summarizes the test cases employed for regression testing and the test results obtained for each test case:

<Yes> or <No>

4.6 TC "\"5.A. CMS Employees and Users of CMS IT Resources\"" \l 2 PERFORMANCE TESTING The table below summarizes the test cases employed for performance testing and the test results obtained for each test case:

<Yes> or <No>

4.7 <TYPE OF TEST>

The table below summarizes the test cases employed for <type of test (e.g., interface testing)> and the test results obtained for each test case:

<Yes> or <No>

5.0 Variances

[Describe any variances between the testing that was planned and the testing that actually occurred. 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.]

6.0 Test Instances

[Provide a brief description of the unexpected results, problems, or defects that occurred during the testing.]

6.1 TC "\"5.A. CMS Employees and Users of CMS IT Resources\"" \l 2 RESOLVED IN TEST INCIDENTS [Identify all resolved test incidents and summarize their resolutions. Reference may be made to Test Incident Reports that describe in detail the unexpected results, problems, or defects reported during testing, along with their documented resolutions, which may be included as an appendix to this document.]

6.2 TC "\"5.A. CMS Employees and Users of CMS IT Resources\"" \l 2 UNRESOLVED IN TEST INCIDENTS [Identify all unresolved test incidents and provide a plan of action for their resolution. Reference may be made to Test Incident Reports that describe in detail the unexpected results, problems, or defects reported during testing, which may be included as an appendix to this document.]

7.0 Recommendations

[Describe what actions are suggested upon completion of this test. Provide any recommended improvements in the design, operation, or future testing of the business product that resulted from the testing being reported. A discussion of each recommendation and its impact on the business product may be provided. If there are no recommendations to report, then simply state as such.]

APPENDIX A: SYSTEM TEST REPORT APPROVAL

The undersigned acknowledge they have reviewed the <Project Name> System Test Report and agree with the approach it presents. Changes to this System Test Report will be coordinated with and approved by the undersigned or their designated representatives.

Signature:

Date:

Print Name:

Title:

APPENDIX B: REFERENCES

[Insert the name, version number, description, and physical location of any documents referenced in this document. Add rows to the table as necessary.]

The following table summarizes the documents referenced in this document.

APPENDIX C: KEY TERMS

[Insert terms and definitions used in this document. Add rows to the table as necessary.]

The following table provides definitions for terms relevant to this document.

Template Version 2.0 (Last Modified on Mar 27, 2009)

PAGE