检测报告英文文档格式.docx

1、ApprovedApprovalReason1.0Author namemm/dd/yyProject Manager namereasonNote to the AuthorThis document is a template of a 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.

2、 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 （） indicates a field that should be replaced with information

3、 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.W

4、hen 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., ） 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 Micr

5、osoft Word （which display a gray background when selected）:a. Select FilePropertiesSummary and fill in the Title field with the Document Name and the Subject field with the Project Name. b. Select FileCustom and fill in the Last Modified, Status, and Version fields with the appropriate information f

6、or this document. c. After you click OK to close the dialog box, update the fields throughout the document with these values by selecting EditSelect 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

7、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

8、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

9、 as blue italicized text enclosed in square brackets. Table of Contents1.0 Introduction 51.1 Purpose 52.0 Test Summary 52.1 Test Type （Function, unit, system, etc.） 52.2 Test Type （Function, unit, system, etc.） 52.3 Test Type （Function, unit, system, etc.） 53.0 Test Assessment 54.0 Test Results 64.1

10、 Unit/Module/System Testing 64.2 System Testing 74.3 User Acceptance Testing 74.4 Ad Hoc Testing 84.5 Regression Testing 84.6 Performance Testing 94.7 95.0 Variances 106.0 Test Instances 106.1 Resolved Test Incidents 106.2 Unresolved Test Incidents 107.0 Recommendations 10APPENDIX A: Test Report App

11、roval 11APPENDIX B: REFERENCES 12APPENDIX C: KEY TERMS 131.0 Introduction1.1 PurposeThis or If the test case failed, list the corresponding Test Incident ID in the Comments column.4.3 User Acceptance TestingThe table below summarizes the test cases employed for user acceptance testing and the test r

12、esults obtained for each test case:4.4 Ad Hoc TestingThe table below summarizes the test cases employed for ad hoc testing and the test results obtained for each test case:4.5 Regression TestingThe table below summarizes the test cases employed for regression testing and the test results obtained fo

13、r each test case:4.6 Performance TestingThe table below summarizes the test cases employed for performance testing and the test results obtained for each test case:The table below summarizes the test cases employed for and the test results obtained for each test case:5.0 VariancesDescribe any varian

14、ces 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 InstancesProvide a brief descripti

15、on of the unexpected results, problems, or defects that occurred during the testing.6.1 Resolved Test IncidentsIdentify 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 rep

16、orted during testing, along with their documented resolutions, which may be included as an appendix to this document.6.2 Unresolved Test IncidentsIdentify all unresolved test incidents and provide a plan of action for their resolution. Reference may be made to Test Incident Reports that describe in

17、detail the unexpected results, problems, or defects reported during testing, which may be included as an appendix to this document.7.0 RecommendationsDescribe what actions are suggested upon completion of this test. Provide any recommended improvements in the design, operation, or future testing of

18、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. Test Report ApprovalThe undersigned acknowledge they have reviewed the Test Report and agree with the approach it presents. Changes to this Test Report will be coordinated with and approved by the undersigned or their designated representatives.Signature:Date:Print Name:Title:Role:Project Manager