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 – String Approach to build cycle unit testing of SAP configuration and developments see section 4.2 – Testing below System Approach to integration testing of SAP modules and developments see section 4.3 – Integration Testing (SIT) below Approach to performance testing of SAP modules and developments see section 4.6 – Performance Testing (PSV) below User Acceptance Testing Approach to support of user acceptance testing see section 4.5 – (UAT) below Approach to continuous involvement of Customer resources throughout testing see section 7.2.2 – <<<CUSTOMER>>> test team roles & responsibilities below Security Approach to the testing of Project defined SAP authorization roles see section 11 – Testing (Roles and Authorizations) below of testing the high-level process scenarios see – – Figure 2 - <<<CUSTOMER>>> High Level Process Scope System Integration Testing (SIT) Considerations for Single Pilot Testing see section 4.3 – below Positive and Negative Testing Approach to Positive and Negative Testing see section 6 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 •
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
BB_158.docx