1 / 45

DART/GSS R42. Test Strategy DRAFT

DRAFT. DART/GSS R42. Test Strategy DRAFT. 3 July 2007. Objectives. The objectives of this presentation is to: Provide a DRAFT level view of current thinking regarding Testing Strategies for Release 4.2

elie
Télécharger la présentation

DART/GSS R42. Test Strategy DRAFT

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DRAFT DART/GSS R42. Test Strategy DRAFT 3 July 2007

  2. Objectives The objectives of this presentation is to: • Provide a DRAFT level view of current thinking regarding Testing Strategies for Release 4.2 • This Strategy will develop further over time but is to be used as an initial “line in the sand” for discussion and further refinement • Areas for improvement identified from R3.1/3.2 are also to be incorporated where applicable. • Further detail on each Test Phase will be documented in Test Approach documents specific to each Test Phase. Slide 2

  3. Table of Contents • Release Scope • Major assumptions • Test Scope • Test Overview/Support responsibilities • Management Overview • Draft Schedule • Environment Requirements • Open Questions Slide 3

  4. Release 4.2 Scope • The following slides contains DRAFT scope for the Release (custodian Anna Bancroft) Slide 4

  5. ANZ 4.2 Scope • GSS Rel 4.2 – AU & NZ Addendum + Localisations • DART • NZ Merchandising Data • Ebydos • NZ & AU ISP CPM Inv • NZ & AU ISP Lubes Logistics Invoices • NZ – GTT Logistics Invoices • AU – Metcash / CStore Logistics Invoices • AU – Cadbury Logistics Invoices • AU & NZ A N Other Logistics Invoices (Ex BizTalk) • Centralised Keyboards in SAP • Merchandising Localisations • SC Localisations for NZ • Some MI NZ Slide 5

  6. ANZ 4.2 Scope – Finance & Merch Slide 6 Slide 6 6

  7. ANZ 4.2 Scope – Supply Chain & MI Slide 7 Slide 7 7

  8. ANZ 4.2 Scope – Site Sjh/acb 06/07/2007 • Not sure about the split on testing phases as e.g. receipt has some content from DART and needs to be included in Integration Test. • No info on receipt layout – no FRD. Emma to provide • DRAFT – comments welcome • List is incomplete - would be good to be clear about which test phases are covering each element. • This is Anna’s list – she has confirmed it is complete. If not accurate then please provide new list Slide 8 Slide 8 8

  9. Items NOT Currently in 4.2 Scope Slide 9

  10. Major Assumptions Sjh/acb 06/07/2007 • Terminology is not quite right US is R4.1 and AU & NZ are 4.2 – the release is R4 • ok • Is third bullet meant to say AU GSS 4.2? • yes • GSS 4.2 contains US and NZ changes • All AU R2.1 GSS sites will be upgraded to R3.2 before R4.2 is deployed in AU • GSS 4.2 Release will not be deployed in parallel to NZ 4.2 • NZ GSS Priorities are: • 1) Loyalty • 2) Rest of generic GSS • 3) ePay/Carwash (order tbc) Slide 10

  11. Major Assumptions (continued) Sjh/acb 06/07/2007 • Tivoli design build will be as per timeframe / approach highlighted in this morning's call. i.e implemented for link test, manual in ITC1 and auto in ITC2 • OK • Tivoli Design/Build will be addressed as per other code deliverables and to same timeframes • All DART and Informatica code/config. delivered and Unit Tested by 11/7 • DART Integration Test Environment (PTZ200) and data delivered as per requirements by 10 August • Test Automation for DART regression testing/data loading will not be available Slide 11

  12. Major Assumptions (continued) Sjh/acb 06/07/2007 • For NZ SC & VMI - would this not be DART test team running the DART elements (as we have done in the UK) as there are developments in INformatica for VMI and the local elements being handled by the local team around Biztalk and integration with vendors. • No – will be done by AU team as discussed with Ajay. VMI is low priority for NZ. • On AU SC Reg Test - what is the long term view for bringing this back into the central test team? • Proposal is that Partha to be involved whilst in AU and transition back to IN • Having split teams brought some challenges in 3.2 – how are we mitigating these risks this time around? • Less risk this time. All Finance done in IN. Will more carefully manage execution – one status report, regular “test” team meetings etc • SC BIZTALK issue causing outbound problem was once off and highlighted design issue – unfortunate that Danny’s test was not visible – bit not justification to centralise all testing • Local DART Testing: • AU Supply Chain Regression Test to be performed by AU Business • NZ Supply Chain/VMI • Others to be confirmed Slide 12

  13. ANZ Test Scope - IN Sjh/acb 06/07/200 • What is not clear to me is who is accountable and responsible for each test phase. Is it possible to have a testing RACI covering all phases • This is what the tables in the pack are meant to show with all names (some blank) by test phase. Suggestions on making clearer • NZ DART 4.2/GSS 4.2 - progression • AU DART 4.2/GSS 3.2 – regression • NZ ETSL Certification Testing • NZ Safety (tbc) • NZ Weights and Measures (NMI) certification required and is to be scheduled Slide 13

  14. ANZ Test Scope - OUT Sjh/acb 06/07/200 • Again I think that this would be clear as a RACI with a clear out of scope slide for all testing - not just what is not being tested in AU. • See later slides • The test strategy should cover the whole release (4.2) not be focussed around one location / team. • Ok agree UK regression is part of overall scope • DART 4.2/R2.1 GSS regression testing • GSS 4.2 DART 4.2 – AU Progression (see Open Questions) • GSS 3.2 to GSS 4.2 Upgrade for AU • UK GSS to DART 4.2 regression testing will be responsibility of UK Test Team Slide 14

  15. NZ R4.2 Major Test Challenges Sjh/acb 06/07/200 • If resourcing is one of the major challenges and we are behind with test prep – as in bullet 5 I would have expected this to be a. higher up the list and b. raised as a project risk at this stage. • Agree – risk not yet officially raised. Sequence in no particular priority • Complexity of Loyalty functionality and number of systems (2 are new) • Requirement to certify with ETSL for all EFTPOS traffic with banks. Requirements are quite strict and accreditation can be lengthy process • Complexity of new test infrastructure (TRANSX, EMV, ETSL) for Loyalty and ePAY • NZ specific pumps – only testable in NZ • LPG Gas bottle fill – unique to NZ • Resourcing – Skilled people still involved in R3.2 yet 4.2 Design/Build/Prep needed Slide 15

  16. Test Phase Overview • The following slides contain placeholders for each of the major test phases envisaged and thoughts to-date • Regression Test will need to be factored into all Test Phases to validate the core functionalities operate correctly as per previous version. Slide 16

  17. Test Phase Summary Sjh/acb 06/07/200 • DART Link test should be renamed DART Product Test OK • Loyalty VDIT should not be down as a formal test phase it is more development / unit test. OK • Link test needs to cover more than just DART / GSS it should include any 3rd party systems for NZ. Agree • GSS Unit Test – Retalix • DART Functional Unit Test – DART • DART Link Test – SAP, Informatica, Tivoli • GSS Product Test – GSS (plus others tbd) • Loyalty DVIT – GSS, Quest, Transx, Loyalty Host • DART/GSS Link Test • Integration Test Slide 17

  18. Test Phase Summary (continued) Sjh/acb 06/07/200 • Project terminology is V&P not P&V. OK • UVT is local deployment resp not testing team . Agree but not quite how it works in AU. Process Team led for 2.1, I did for 3.2. No DART Deployment team in AU • User Verification Test • DART P&V Test • DART OPS Test • GSS P&V Test • GSS OPs Test • ETSL Certification Test • Cutover Test (in Pre-Prod) Slide 18

  19. NZ 4.2 Loyalty – Summary Architecture DART ISP start POSDM INFORMATICA Outbounds Inbounds XcelleNet GSS Loyalty Host, RUCSFuel Card Host POS Quest TRANSX Hosts ETSL Banks Slide 19 19

  20. Product/Link Tests • There is a need for proper Link Testing for each of the major interfacing systems prior to Integration Testing to minimise schedule and quality risk as observed from both UK 3.1 and ANZ 3.2 Testing • It is proposed for 3 separate “Product” Tests: • 1. GSS Product Test • 2. DART, Informatica and Tivoli Product Test • 3. Complete DART/GSS Link Test Slide 20 20

  21. NZ 4.2 Loyalty – Test Phase scope Sjh/acb 06/07/200 • Not sure what the open questions around scope of PT are- when / what is the forum and timeframe for getting these resolved? This is obviously urgent and risks duplication / gaps. • Dependant on Integration Test DART Product Test DART ISP start POSDM INFORMATICA Note: Scope of GSSProduct Test tbd Outbounds Inbounds XcelleNet GSS Loyalty Host, RUCSFuel Card Host POS Quest TRANSX Hosts ETSL Banks Loyalty VDIT Slide 21 21

  22. Loyalty Vendor Development Integration Test • A separate Vendor Development Integration Test (DVIT) is planned as part of Loyalty development. This will include GSS, Quest, Transx, AA Host • Retalix, Quest and NZ resources already scheduled for this • Highly interactive testing expected to validate/fix technical solution prior to formal integration testing Slide 22

  23. SAP – MER / FI Outbound / Inbound Informatica Xcellenet POS DM / BW GSS Other 2. Execution & Support GSS Product Test Sjh/acb 06/07/200 • Need to confirm execution support resources • I have asked Anna and Ajay – this is all I have Slide 23

  24. Execution & Support – DART Product Test Sjh/acb 06/07/200 • Need to get confirmation on DART PT approach & resourcing - otherwise there is a risk that this phase will slip SAP – MER / FI Outbound / Inbound Informatica POS DM / BW GSS Other Slide 24

  25. 3. DART/GSS Link Test • This Test Phase to be a precursor to formal Integration Test • Major Scope • Tivoli shakeout of End to End batch flow • DART Outbound files to GSS via Informatica XcelleNet • DART Inbound files from GSS via XcelleNet • ISP Mailbox • Master Data validation between DART and GSS Slide 25

  26. DART/GSS Link Test Sjh/acb 06/07/200 • Are those exit criteria achievable? (Believe not) • Suggestied amendment s- this is standard. • Could include functional view – FFR and Outbound from DART to GSS and successful inbound, 1 Loyalty transaction E2E etc • Need to focus on the big ticket items here like getting resourcing and location landed • Focus: Cross platform internal technical integration. • Objectives: Validate that major internal interfaces are correctly operating prior to formal Integration Testing • Execution Notes: Resourcing & locations to be confirmed • Environment/data/equipment: Requirements to be confirmed for each test based on agreed boundaries • Entry criteria: All development complete, test environment and data available, roles & responsibilities agreed, Test Readiness Reviews completed • Exit criteria: No Critical, Urgent or High issues open. Slide 26 26

  27. Execution Support – DART/GSS Link Test SAP – MER / FI Outbound / Inbound Informatica Xcellenet POS DM / BW GSS Other Slide 27

  28. Integration Testing Focus: NZ & AU deployment of GSS/DART 4.2 and R32 AU regression Testing Test ideas: Loyalty: Ensuring that the following cards/coupons are covered during NZ testing: AA and THL cards, Gift Cards, Discount Coupons, Fuel Dockets, Wild Bean Pre Pay, other. (Note: AA Cards represent 30% of transactions) LPG Bottle Refill (verify correct conversion of KGs into litres to POS for sale) Testing will ensure that backend systems as well as 3rd party systems for AU and NZ, namely eOrders, Loyalty and ETSL can be verified to work as expected. In addition, ETSL needs to pass certification in NZ. Objectives: System is integrated ensuring that store systems, backend and 3rd party systems can work as expected and results are verifiable. Potentially include ETSL Certification in parallel on NZ. Rigs will be connected to bank for certification verification. Ensure the integrity of the process with customer’s money. Sjh/acb 06/07/200 • NZ EDI needs to be in scope as well as AU • NZ VMI? Slide 28

  29. Integration Testing (continued) Execution Notes: need to conduct some tests in NZ due to equipment requirements (tbc -Palmerston Nth as near to ITL) Environment/data/equipment: LPG Bottle, NZ configuration test rigs, EMV enabled pinpads, Transx link, ETSL connectivity, EMV Test cards (Valid, invalid, damaged, blank), Rigs, pumps, pump controller, carwash, ATG? Entry criteria: No defects open that can impact testing. Environment and or test rigs available. Exit criteria: No Sev1, Urgent or High issues open. Sjh/acb 06/07/200 • How / what parts of integration testing are going to be done elsewhere? Is that then integration Testing? How will this be managed & status reported etc • Things that can only be done in NZ – eg pumps, camera integration etc • Again think we need to look at exit criteria • Suggestions? Slide 29

  30. Execution Support – Integration Test SAP – MER / FI Outbound / Inbound Informatica Xcellenet POS DM / BW GSS Other Slide 30

  31. UVT Sjh/acb 06/07/200 • This is not generally part of testing team's responsibility. • Process Team/Business to own – but Test Team support. Still important to include in Test Strategy as it is a Test Phase • Process focussed • Need a business/process Lead to own this test phase • Process guides/training material needed as part of Test Prep. • Expectations are same as for R3.2 (need business reps. to execute tests) Slide 31 31

  32. Execution Support – UVT SAP – MER / FI Outbound / Inbound Informatica Xcellenet POS DM / BW GSS Other Slide 32

  33. Volume & Performance Testing Sjh/acb 06/07/200 • Need to confirm transaction times against NZ legacy system for GSS – not 3.2 baseline • Need confirmation on ownership & accountability for these test phases • GSS • Regression testing against 3.2 baseline • Others? • DART • AU/USA/NZ batch performance • Others tbd Slide 33

  34. Execution Support – DART V&P Test SAP – MER / FI Outbound / Inbound Informatica Xcellenet POS DM / BW GSS Other Slide 34

  35. Execution Support – GSS V&P Test SAP – MER / FI Outbound / Inbound Informatica Xcellenet POS DM / BW GSS Other Slide 35

  36. Operations Testing Sjh/acb 06/07/200 • Need confirmation on ownership & accountability for these test phases • GSS • tbd • DART • AU/USA/NZ “sociability” testing (batches etc) • Others tbd Slide 36

  37. Execution Support – GSS Operations Test SAP – MER / FI Outbound / Inbound Informatica Xcellenet POS DM / BW GSS Other Slide 37

  38. Execution Support – DART Operations Test SAP – MER / FI Outbound / Inbound Informatica POS DM / BW GSS Other Slide 38

  39. Execution Support – DART Operations Test SAP – MER / FI Outbound / Inbound Informatica POS DM / BW GSS Other Slide 39

  40. Management Responsibility - GSS Sjh/acb 06/07/200 • Kim Morley is actually Responsible for Retalix code deliv / management and he reports into Derek • Lots of TBCs here - need to get this landed Slide 40

  41. Management Responsibility - DART Sjh/acb 06/07/200 • Again lots of TBCs Slide 41

  42. Management Responsibility - General Slide 42

  43. DRAFT Schedule/Test phases Sjh/acb 06/07/200 • Need to keep aligned with the US test cycles - which is the baseline plan - patches which are shared with US will then be aligned across the 2 releases. • Need to confirm patch releases with Kim Slide 43

  44. Environment Requirements - DRAFT Sjh/acb 06/07/200 • It has not been decided that AU 4.2 PT is out of scope. • Chris can help fill in the blanks on the BDC area. I believe that they are getting a codax unit from Retalix Slide 44

  45. Open Questions Sjh/acb 06/07/200 • There are some big questions here which are urgent to get resolved • Need to land QC question & defect mgmt tool question and make sure that these changes are clearly communicated out. This is urgent if we are to manage the change to the team to enable it to be used for 4.2 and do test runs etc • Release mgmt will not be joint meetings but sep meetings with the centre for each country I believe • Clarification on On-Shore / Off Shore is also needed and make sure that the prep is aligned. • Use of Quality Centre for test execution ? • Defect Management tool • US/ANZ Test Joint Release/Defect Management • DART on-shore v off-shore responsibilities • AU Management have requested that AU GSS 4.2 to DART 4.2 be included in scope to position for AU deployment if required. Resource implications to be assessed and funding source determined Slide 45

More Related