The document outlines an integration testing plan led by Andy Scarr, detailing completed steps, such as scenario identification and test scripting for releases 1 and 2. It includes guidelines for creating structured test scripts, naming conventions, and the necessary resources for execution. Next steps involve kick-off meetings, scenario identification, and scheduling for test script writing and execution phases.

1. 10/25/11 1st July 2009 Andy Scarr

2. Agenda Integration Testing Overview Recap : Steps completed Test Scripting – A Deep Dive Next Steps 10/25/11 Andy Scarr

3. Overview of the Integration Test Cycles Test E2E processes with RICEFW for Release 1 &2 10/25/11 Unit testing IT Cycle 1 Data dry Runs& dress rehearsal Regression Test Readiness Test Go-Live Scope of Testing Time IT Cycle 2 2 Solution Illustration Testing IT Cycle 3 IT Cycle 2 Test configuration for R1 and R2 IT Cycle 2 R1 – E2E standalone testing for R1 R2 – E2E testing with large Gaps Andy Scarr

4. Steps completed so far … Integration Testing Kick-Off Scenario identification Identification of scenario’s (both for R1 and R2) Rationalisation of scenario’s Identification of variant’s Cross-Stream dependencies Identification of touch-points between work-streams Identification of “sequencing” of processes Identification of data objects Identification of SAP Organization Structure elements 10/25/11 Andy Scarr

5. Structure 10/25/11 E2E Process Scenario-1 Scenario-2 Scenario-N Variant-1 Variant-2 Variant-1 Variant-1 Test Script 001 Test Script 002 Test Script 003 Test Script XYZ Embedded Template Removed for Security Reasons Andy Scarr

6. What is a Test Script ? A test script ensures that an E2E process test is done in a structured and repeatable manner Leads the tester step by step through the screens and includes the data that is relevant for this test A word document which contains the following sections : Test Script ID, Version Control, List of pre-requisites (data, configuration, etc) Input data (master data, data “inherited” from the previous scripts) Detailed description of sequential steps (consisting of transaction codes, menu paths, step-wise instructions, expected results, etc) 10/25/11 Test Script Template (contains sample test script) Embedded Template Removed for Security Reasons Andy Scarr

7. Test Script Naming Convention 10/25/11 Andy Scarr Character Values Description Remarks First 2 characters R1 R2 Release-1 Release-2 Identifies relevance for which release Next character - Separator (Hyphen) Next 2 characters FIN WFM EAM PRC HCM Finance Work Force Management Asset Management Procurement Human Resources Identifies process area Next character - Separator (Hyphen) Next 4 characters XXXX Sub-processes within a team To be decided by the process teams Next character - Separator (Hyphen) Next 10 characters YYYYYYYYYY Description To be decided by the process teams

8. Critical Points Each test script will have an “owner” Team Work is critical : test scripts might cut across work-streams – necessary coordination will be done by the “owner” to get timely inputs from other work-streams Final Test Scripts will be uploaded in Mercury Quality Center (Testing Tool) Testing execution, Progress Monitoring will be carried out in QC Defect reporting and resolution tracking will be in QC QC training will be provided to testing team before start of execution 10/25/11 Andy Scarr

9. Where to keep the Test Scripts ? S:\·Interdepartmental Teams\EAM_ERP\01 SAP Programme\08.010 Integration\08.010.20 Realisation\08.010.20.50 Integration Testing\08.010.20.50.20 Test Scripts 10/25/11 Andy Scarr

10. Configuration, Data, Roles, Developments Testing of E2E processes (through test scripts) will need availability of configuration, data, roles, developments before start of testing processes in the dedicated Testing Environment For ITC1 : Configuration will be automatically available in Testing Environment Minimal data (~ 5 data objects) will be pre-loaded in Testing Environment by Data Team Rest of Data needs to be created in Testing Environment manually by the work-streams before start of ITC1 Data needs to be mapped to individual test scripts Generic user-ID’s with necessary roles will be provided before testing execution Developments will not be tested in ITC1 10/25/11 Andy Scarr

11. Next Steps - Following the Integration test plan 10/25/11 16/06-25/06 Kick Off Meeting – 15/06 Identify test scenarios & Cross stream walkthroughs Till 24/07 Write test scripts 27/07-14/08 C1 Execution 31/08-25/09 C2 Execution Set up Environments Build Roles for testing Infrastructure Readiness Testing resource readiness Create data for testing Andy Scarr