Purpose This document outlines the way in which the testing will be performed for the <<<CUSTOMER PROJECT NAME>>>. This includes which testing phases to include, scope definition, time frame of testing, physical location of tests, organization of testing phases and issue resolution. This document aims to describe the following elements of testing: Definition of test phases – see section 4 Test Phases below Entry and exit criteria for each test phase – see section 4 Test Phases below Testing responsibilities and resource requirements – see section 7.2 Roles & Responsibilities below Approach to build cycle unit testing of SAP configuration and developments – see section 4.2 String Testing below Approach to integration testing of SAP modules and developments – see section 4.3 System Integration Testing (SIT) below Approach to performance testing of SAP modules and developments – see section 4.6 Performance Testing (PSV) below Approach to support of user acceptance testing – see section 4.5 User Acceptance Testing (UAT) below Approach to continuous involvement of Customer resources throughout testing – see section 7.2.2 <<<CUSTOMER>>> test team roles & responsibilities below Approach to the testing of Project defined SAP authorization roles – see section 11 Security Testing (Roles and Authorizations) below of testing – the high-level process scenarios – see Figure 2 - <<<CUSTOMER>>> High Level Process Scope Considerations for Single Pilot Testing – see section 4.3 System Integration Testing (SIT) below Approach to Positive and Negative Testing – see section 6 Positive and Negative Testing below Risks and their mitigation strategy & assumptions – see section 14 Risks, Issues, Assumptions, Dependencies & Decisions (RAIDD) below Acceptance criteria for build cycle unit testing, integration testing, performance testing, and user acceptance testing are detailed in section 4 Test Phases below. Following approval of the Testing Strategy document, and completion of the solution workshops, detailed test plans will be produced for each phase of testing. Context and Intended Audience The context of this strategy specifically applies to the <<<CUSTOMER PROJECT NAME>>> Project. The intended audience for this document includes, but is not limited to: AS APPROPRIATE>>> • Project management from <Client Name> Project Teams and SAP as approvers
<<<CUSTOMER>>> Test Master Data Coordinator Own the master data co-ordination for <<<CUSTOMER>>> testing Gather test data requirements from testers and functional consultants Liaise with the master data team and SAP test data coordinator to gather correct and valid data for testing Liaise with SAP test automation team to generate test data if applicable Manage number ranges to ensure segregation of data Liaise with legacy teams and SAP test data coordinator to ensure valid data is in the appropriate systems Obtain migrated data that is relevant and applicable for use for testing Report to the <<<CUSTOMER>>> test manager and escalate issues and risks <<<CUSTOMER>>> Test Defect Manager Chair daily defect triage meetings in a structured manner for UAT and legacy system related defects Challenge and follows through defect resolution to an acceptable outcome to both the program and the teams involved Provide arbitration and defect process guidance Conduct defect administration, including providing daily reports and updates Provide test team with defect retesting list Scope to cover UAT and legacy system defects Can provide custom reports and configuration in Solution Manager 7.2 to suit the needs of the project. Tester Works with SAP Performance Test Lead to take over the performance testing assets once SAP have completed the performance testing phase Takes action on the recommendations provided by the SAP Performance Test Lead Progresses performance testing for <<<CUSTOMER>>> as required Automation Tester Work with SAP Automation Test Lead to take over the automation testing assets once SAP have completed the automation testing phase Maintain the regression test automation deck for <<<CUSTOMER>>> Create any test data required using automation scripts for <<<CUSTOMER>>> testing Progresses automation testing for <<<CUSTOMER>>> as required Manual Tester / Key Business User / Testing Leads Prepare test scenarios for UAT Prepare test for data variant testing and UAT Prepare test data requirements for <<<CUSTOMER>>> test data coordinator Peer review test scripts Execute test scripts Defect tracking, retesting and assisting in defect resolution Communicate with <<<CUSTOMER>>> test manager, functional consultants and build team Resource Schedule A detailed schedule of resources for SAP testing can be in the following attachment. The resources align to the project plan as at the time of writing. The resources schedule may change as required to suit project needs, and will be owned by the SAP Test Manager, and managed by the SAP test leads. <<<ADD A RESOURCE SCHEDULE TO SHOW WHICH RESOURCES WILL BE DEPLYOED WHEN AS PER THE PLAN ON A PAGE>>>
Defect Management Process Figure 16 - Test defect raising and resolution process describes the defect management process that will be used during the program. Figure 16 - Test defect raising and resolution process AS APPROPRIATE>>> Responsibility The Defect Manager will manage the defect resolution process as follows: Defect manager will ensure Solution Manager 7.2 is updated with defect details and status Defects will be assigned to the appropriate area for resolution. No transport migrations will without a defect id being provided. Technology or Business will update any necessary documents where updates to requirements required as part of a defect resolution. Development / build teams will provide fixes as part of the defect resolution where a design or code change has been identified or The Defect Manager will convene regular defect meetings to co-ordinate severity and priority of defects raised, for timely resolution of defects. The tangible documentation that form the testing deliverables are: Table 7 - List of key deliverables Deliverable Deliverable Description Project Phase Dependencies Test Strategy This document sets the strategy for testing that will be conducted by the SAP test team (in conjunction with <<<CUSTOMER>>>) for the program Explore <<<CUSTOMER>>> Test Policy PSV Test Approach Document used during the kick-off to advise the team of the test approach for that test phase. It will contain the test plan to show what tests will be created in this phase Realize Test Strategy String Test Closure Report Document that summarizes the test phase after execution. It documents the test activities and the final results that will allow stakeholders to decide on whether to pass the test phase. Realize Test Results, Exit Criteria in Test Strategy