Master Test Plan主测试计划.docx

InstructionThis document is used to define the details of the master test plan. Once the test plan is outlined, the document must be reviewed and approved by the lead technical representative on the project as well as the lead business representative on the project. If anything related to the test plan changes during the execution and testing phase of the project, this document should be updated and re-approved by both parties.Test ScopeThis section is used to provide a high-level description of the business processes to be tested and a high-level description of the type of testing required for this project. It also defines what is not in scope for the testing phase of the project.Example: This test plan will test all the requirements for System A release 1.1 with the exception of requirement nnn, which will be tested by the xxxx team for xxxx reasons. This Master Test Plan covers integration, user acceptance, and regression testing. It will not include unit testing, which will be performed by the external vendor, ZZZ. It will not include user certification testing, which will be performed by the Finance Team. Test FeaturesThis is a description of the features that will be tested within the scope of the test plan. The list represents what will be tested as well as the individuals/groups involved with the testing activities.Example: BR #FeatureResponsible party or groups1Pre-Clean (incorporate Worksites version)IT2List Bills (incorporate Worksite standards)IT, A/P Director3Direct Bills (incorporate Worksite standards)IT, A/P Director4Dynamics (to incorporate the FTP piece to the Austin server for Sarbanes Oxley)IT, ControllerTest Inputs/OutputsThis is a description of the inputs that will be used to assist with the testing effort and a list of the outputs that will be delivered from the testing effort. Example: InputsOutputsBusiness Requirement SpecificationsTest ResultsDefect LogIssues LogChange Request LogTest StrategyThis is a description of the recommended testing approach for this project. This describes “how” the test items and features will be tested. Example: Test TypeDescriptionCommentIntegration Test This type tests all changed functionality end to end.User Acceptance Test Typically performed by Business User, this tests all changed functionality of a system from the end-user perspective.Regression Test This tests the entire system to insure that any untouched functionality did not get adversely impacted by the project-related work.User Certification TestThis test is performed after the solution has been moved to production to insure it has been moved successfully.This will be performed by the Business User.Test Environment (tools, system, databases)This is a list of the testing tools, systems, and databases. Example: ToolsDescriptionVersionWinRunner Automated script generation tool.4.0LoadRunner Automated script generation tool.2.3Unix Shell ScriptsScripting language.In houseManual inputManual entry of data onto screen or gui.n/aClearCaseTool used to track defects.In house toolSystemTest SystemCinappxxxPC Lab13th floorDatabaseTest database 1/testdatabase0001Test database 2/prodatabase002Test Roles and ResponsibilitiesThis is a list of the testing roles and responsibilities. Example: ResourceRoleResponsibilityTom Thomas, NUITTest Manager/Project Manager Provides technical direction. Acquires testing resources. Assigns tasks to testing resources. Communicates test results to management.Steve Stevenson, NUITTest Designer Documents test plan. Identifies, documents and prioritizes test cases. Evaluates effectiveness of test effort.Joan Jones, FinanceChris Christopher, NUITTester Executes test cases, logs defects, and documents test results.Rob Robinson, NUITTest System Administrator Ensures test environment and assets are installed, managed and maintained. Includes administration of testing ids.Test MilestonesThis is a list of the critical test milestone dates. Be sure to include these dates in the overall project plan.Example:TaskMilestone DateSetup Test Environment07/31/05Complete Unit Testing08/31/05Complete Integration Testing09/30/05Complete User Acceptance Testing10/31/05Complete Regression Testing11/30/05Complete User Certification Testing12/31/05Document ApprovalThe signatures below acknowledge that the test plan outlined above is complete and accurate. Upon receiving written approval, the project team will proceed to the next step of the project. If anything changes during the execution of the project, the test plan will be updated and re-approved accordingly.Approv