HASCO运营管理信息系统UserAcceptanceTestSummaryReport模板.doc

User Acceptance Test Summary Report Current Version: Owner: Date Last Updated: Last Updated By: Author: Date Created: Approved By: Approval Date: User Acceptance Test Summary ReportDoc. Version m.nn SDP-21Template Version 1.0 Page 2 of 9 Revision History Version Number Date UpdatedRevision AuthorBrief Description of Changes Instructions: For the suggested topics below, replace with project specific information. Some of the topics may not apply to all projects. In the topics where a response is optional, a choice, “N/A for this report” is included in the instructions. User Acceptance Test Summary ReportDoc. Version m.nn SDP-21Template Version 1.0 Page 3 of 9 Table of Contents 1INTRODUCTION.4 2ACCEPTANCE TESTING - TEST RESULTS 4 2.1TEST BUILD AND INSTALLATION - DEFECT SUMMARY.4 2.2BUILD AND INSTALLATION CHECKLIST.4 2.3BUILD AND INSTALLATION SUMMARY.5 2.4ACCEPTANCE TESTING - TEST CASES SUMMARY.5 2.5ACCEPTANCE TESTING - DEFECTS SUMMARY5 2.6ACCEPTANCE TESTING - TEST PASS CHECKLIST5 2.7ACCEPTANCE TESTING - SUMMARY.6 User Acceptance Test Summary ReportDoc. Version m.nn SDP-21Template Version 1.0 Page 4 of 9 1 Introduction Document the summary of the User Acceptance test results and validate the results Project ID: Test Cycle Reference: Number of Test Cycles Reference Documents: 1.1 Test Item Summarize the evaluation of the test items. Identify the items tested, indicating their version/revision level. Indicate the environment in which the testing activities took place. Tested Items: Version/revision Level: Environment: Location: 1.2 Reference For each test item, supply references to the following documents if they exist: test strategy, test plan, test case, test readiness, and test defects. Test Strategry: Test Plan: Test Case: Test Readiness: Test Defects: or all defects can be found in test tool Quality Center. 1.3 Variances Report any variances of the test items from their design specifications. Indicate any variances from the test plan, test cases, or test environment. Specify the reason for each variance. Variances From Test Plan: Variances From Test Cases: Variances From Test User Acceptance Test Summary ReportDoc. Version m.nn SDP-21Template Version 1.0 Page 5 of 9 Environment: 1.4 Comprehensiveness Assessment Evaluate the comprehensiveness of the testing process against the comprehensiveness criteria specified in the test plan if the plan exists. Identify features or feature combinations that were not sufficiently tested and explain the reasons. Criteria 1: Assessment: Features or Feature Combinations: Explain Reasons: Criteria 2: Assessment: Features or Feature Combinations: Explain Reasons: 2 Acceptance Testing - Test Results Consolidate the summary of the Acceptance test results and report them here. 2.1 Test Build and Installation - Defect Summary Severity of DefectsHighMediumLow Acceptance Testing Cycle 1 Acceptance Testing Cycle 2 Acceptance Testing - Cycle-N Total Defects Acceptance Testing 2.2 Build and Installation Checklist Verify against the checklist below. Add additional checklist items, as necessary NoChecklist ItemYes/No/NA 1Have all the latest version of the source binary code files been delivered by the supplier in the appropriate folders as mentioned in the release notes? 2Was the System build successful? User Acceptance Test Summary ReportDoc. Version m.nn SDP-21Template Version 1.0 Page 6 of 9 3Are the system installation steps consistent with the steps documented in the Installation Guide? User Acceptance Test Summary ReportDoc. Version m.nn SDP-21Template Version 1.0 Page 7 of 9 2.3 Build and Installation Summary Document any additional information that needs to be informed to the Senior Management and the End-Users. Include information on why the system was allowed to move to the next phase with identified defects or why the Build has failed. Mention any lessons learned and any corrective actions taken 2.4 Acceptance Testing - Test Cases Summary Type of Testing Number of Acceptance Test Cases prepared Number of Acceptance Test Cases executed Number of Acceptance Test Cases passed Number of Acceptance Test Cases failed Acceptance Testing Cycle 1 Acceptance Testing Cycle 2 2.5 Acceptance Testing - Defects Summary Severity of DefectsHighMediumLow Acceptance Testing Cycle 1 Acceptance Testing Cycle 2 Acceptance Testing - Cycle-N Total Defects Acceptance Testing 2.6 Acceptance Testing - Test Pass Checklist Verify against the Acceptance Testing Pass criteria as documented in User Acceptance Test Plan (UATP). S No Checklist ItemYes/No/NA 1.Have all the User Acceptance Test Cases been executed? 2.Are all the reports as required in the System Requirements Specification (SRS) generated correctly? 3.Has the success criteria percentage of pass and severity of defects as documented in the User Acceptance Test Plan (UATP) been met? 4.Are the hardware and software versions used for testing consistent with the IT Standards BOM? User Acceptance Test Summary ReportDoc. Version m.nn SDP-21Template Version 1.0 Page 8 of 9 S No Checklist ItemYes/No/NA 5.Have all the non-functional test cases as documented in the Acceptance Test Case Document been executed? 6.Has the list of documents that are part of the System Documentation been provided? 7.Have the operational requirements for in the SRS been satisfied? 8.Has the pass criteria percentage of pass and severity of defects as documented in the UATP for Non-Functional tests been met? 2.7 Acceptance Testing - Summary Document any additional information that needs to be communicated to the Senior Management or End-Users. Include information on why the system was allowed to move to the next phase with identified defects, or why the test failed. 3 Evaluation Provide an overall evaluation of each test item including its limitations. This evaluation shall be based upon the test results and the item level pass/fail criteria. An estimate of failure risk may be included. * This evaluation should be done by STE (Senior Testing Engineer) or above staff who has many advanced evaluation skills. If there are no STE or above in project, Project Manager should do evaluation based upon all Testing Engineerss suggestions. 4 Summary of Activities Summarize the major testing activities and events. Summarize resource consumption data, e.g., total staffing level, total machine time, and total elapsed time used for each of the major testing activities. Staffing Level and Name (Staffdays) Testing Engineer: Senior Testing Engineer: Other Staffers: Acceptance Test Plan and Relations: Acceptance Test Case and Relati