1 / 15

Testing Deep Dive

Testing Deep Dive. ITC3 Current Status – Condition/Day View. ITC3 Completion to date – 80% executed / 73% passed By end of day Friday, best case picture is that we could be at 90% executed / passed based on retests going on. Process Chain – Current View. Process Chain – Forecast View.

fleur-solis
Télécharger la présentation

Testing Deep Dive

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. Testing Deep Dive

  2. ITC3 Current Status – Condition/Day View • ITC3 Completion to date – 80% executed / 73% passed • By end of day Friday, best case picture is that we could be at 90% executed / passed based on retests going on

  3. Process Chain – Current View

  4. Process Chain – Forecast View • By end of day Friday, best case picture:

  5. ITC3 – Current Status Summary Before we dive into the detail by process chain, high-level view is: • While we have executed 80% of test model • We need patch 15 to be able to complete c. 10% of the outstanding testing • We need fix to TPR 3598 to be able to complete c. 5% of the outstanding testing We clearly have not reached our ITC3 Exit Criteria by today’s PRB as forecast last week, due to TPR’s • With arrival of patch 15 next week and fixes to DART, we will be able to re-test outstanding conditions • Recommend that we keep the meter running and update status reporting for ITC3 as fixes are received and conditions are passed • whether we exit ITC3 or not, the activities are exactly the same

  6. ITC3 – Process Chain Commentary • Tax Process Chain • ITC3 • 18 conditions passed • TPR3593 (HIGH) needs to be in patch 15 - tender and item totals do not match in POSDM. • TPR 3864 (MEDIUM - Fix in progress) –not go live critical • Other conditions on hold because of Environment restrictions • Fails relate to IL, FL conditions and as such are not go live critical

  7. ITC3 – Process Chain Commentary • Ordering • ITC3 • 7 Conditions have passed • TPR3792(HIGH), TPR3824(Medium), TPR3828(HIGH) and TPR3854(HIGH) - retest in progress. • The failed conditions will be run executed over Wednesday and Thursday this week for Coremark • All failures relate to invoices

  8. ITC3 – Process Chain Commentary • Royalty – SAP RE • ITC3 • 9 conditions passed • TPR3862 (HIGH) in patch 15

  9. ITC3 – Process Chain Commentary • Fuel • ITC3 • 21 conditions passed • TPR3875 (HIGH) in patch15 • TPR3386 (HIGH) on hold as can not be tested until record type 13 is fixed • TPR3784 is a very high defect it does not populate record type 13 so it shows fuel variance • TPR's in patch 15 needed to address 7 of the failed conditions.

  10. ITC3 – Process Chain Commentary • Space and Range Process Chain • ITC3 • 4 condition passed • Cara is now executing these on her laptop with help of an IBM resource here

  11. Product Test Key Functionality – RAG Status

  12. R4.1 Product Test Defects • The table below includes all PT defects that are relevant to the R4.1 deployment by priority • The table below includes all PT defects that are relevant to the R4.1 deployment by agreed release

  13. Defect Comparison with R2.1 & R3.1 • The total number of valid defects raised against each release is – • R2.1… 1195 defects (P1 = 90, P2 = 505, P3 = 365, P4 = 235) • R3.1… 856 defects (P1 = 55, P2 = 427, P3 = 287, P4 = 87) • R4 (to date)… 1667 defects (P1 = 97, P2 = 947, P3 = 518, P4 = 105) • The total number of defects fixed in the pre-pilot release was – • R2.1… 81 defects (P1 = 6, P2 = 60, P3 = 7, P4 = 8) • R3.1… 65 defects (P1 = 10, P2 = 28, P3 =24, P4 = 3) • The total number of defects open at pilot against each release was – • R2.1… 80 defects (P1 = 0, P2 = 16, P3 = 43, P4 = 21) • R3.1… 68 defects (P1 = 6, P2 = 27, P3 = 27, P4 = 8) • For R3.1 the 6 P1 issues were hot fixed for the first pilot site

  14. Next steps • Key issue is limited repeated coverage of business critical functionality in product test • Increase testing scheduled on WoR build for 7130.15 regression • Complete additional WoR testing in US lab if spare capacity (environment & resource) • Drive forward resolution for blending in BDC (hardware now available) Review requirement to complete blending testing in US • Confirm with EPS test team that key functionality e.g. Pay at Pump tested and rubber-stamped • Key risk is the high level of change in the pre pilot release (7130.15). Next actions are – • Decrease the scope of 7130.15 and agree with country deployment team list of open issues (suggest all medium descoped at min) • Plan additional hot fix release (7130.15.01) for any P1 & P2 required for pilot • Plan additional full release (7130.16) with associated regression test (note – this may drive out pilot date)

  15. Next steps • W/C 5/11/7 • Product Test completing PT4 • Scoped based on risk areas, focussing on WoR fuel • Running on patch 14 • W/C 12/11/7 • Product Test of Patch 15 • Regression pass to ensure previously working functionality not broken • Retesting of fixes delivered in patch 15 • Focus on areas of risk – WoR fuel • Integration Test • Retesting conditions fixed with patch 15 (c. 20 currently) • Regression test of any areas subject to high churn (analysis in progress) • W/C 19/11/7 • Product Test • Patch 15.01 – fixes to any go-live critical issues coming out of patch 15 testing • Integration Test • Retesting conditions fixed with patch 15.01

More Related