1 / 5

GSS R4.1 Product Test Status

GSS R4.1 Product Test Status . R4.1 Functionality – RAG Status. 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.

teenie
Download Presentation

GSS R4.1 Product Test Status

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. GSS R4.1 Product Test Status

  2. R4.1 Functionality – RAG Status

  3. 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

  4. 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

  5. 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)

More Related