1 / 24

Statoil Fuel & Retail

Statoil Fuel & Retail. ITDay 2 Test strategy planning – End User Testing. Introduction to test. Infrastructure test:

anjolie-tate
Download Presentation

Statoil Fuel & Retail

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. Statoil Fuel & Retail ITDay 2 Test strategy planning – End User Testing

  2. Introduction to test Infrastructure test: To ensure that infrastructure, access, network, connections, Microsoft office, sharepoint, applications, etc.. Is working properly after migration to new IT infrastructure platform and windows7, the solution must be tested.- Windows7, Lync, Sharpoint to work with new features (also migrated <> non migrated) - Applications (incl. interfaces) must work as-is before/under and after migration The first testing will be ‘EUC, ECS and ESS testing’, followed by application testing when migration of this will start. Test Management Plan: Link

  3. Roadmap and milestones

  4. Proposed timeline / roadmap Preparation Implementation Transition Project Management Interim IT Architecture To-Be IT Architecture Deployment, Versions Control and Release Mgt. 15-11-2010 1-10-2012 ((at the latest)) Exit Plan Interim IT architecture in place Interim svc.mgmt. in place Delivery Agreement finalized separation completed Datacenters Data / storage Migration Network (LAN/WAN) WAN: move external Access mgmt. WAN/LAN: transition internal Desktop Mgmt. Servers, establish new and ”box move” Remote access Basis for transitioning applications Integrationplatform Appl- platforms Sharepoint/Notes/.. Transition vertical apps Successive transitioning of applications Client rollout SAP copy / ”Clone and delete” Move users Replace or transition H apps Organization, governance, service management processes & tools etc. Organization, governance, service management processes & tools etc.

  5. Transition Pilotplan - Test Pilot Definition Ready Communicate to Pilot Users Sign off Content & Publish Town Hall Meeting End Users Transfer traing material to UAT and Pilot users End User Material Ready (SRM,ITSM, SD Win7, Office, Interim) SD, ITSM,SRM ready Hard Go Live Green Field Pilot Start Soft GoLive (Must be approved) 15-25 Users x 2 Onsite Ready and Rampup Agreed EUC Testing Ready (CPH, STH) ESS Build Ready 2 x 6 lap/desk-top update Done(After Greenfield test) HW orders placed for Testing Migration (AD, File, SP) Completed Pilot Users identified HW orders placed for Pilot Rollout Start Pilot Users Start GreenField Testing Done (CPH, STH) 6 test lap/desk-tops x 2 (CPH & STH) Printers Order placed Functional User Acc Test Complete & approved UAT Users identified

  6. System Landscape to be tested

  7. Test strategy, plan and Invironment Test Strategy Test Plan Guidelines Test Plan(s) Test conditions 2 x 6 lap/desk-tops is migrated and test invironment will be established for testing. Several tests may be executed simultaneously in the same test environment. Test Cycles • Test Criterias: • - Test Checklist (scripts) • - Test data Description • Test execution- Expected results* Cap Gemini - Unit / System test (infra) Test Report • SFR (Int / Processes) • Greenfield (Project) • User Acc.Test (Business) Physical Data • Criterias of expected results:Daily proceses must work (must be tested by selected users (HQ, leaders, depots, customer service, back office, IT etc)Int.test: All interfaces (via biztalk etc..) must work also after migrationAcces and applikations must work ‘as-is’

  8. Test Approach • Infrastructure Test (Cap Gemini)- Unit test- Int. test (small)- System test • Greenfield test (SFR) (15/11 - 25/11 (1/12)) • System test - Int. test • Functional User Accept. Test (5/12 – 23/12) • System test - Int. test- Process test • 9/1-2012: Soft Go-live (Pilot) * • 6/2-2012: Hard Go-live Test fase 1(Infrastructure) Responsible: Cap Gemini Test fase 2 (Greenfield)Responsible: SFR Test fase 3 (Before Go-live)Responsible: SFR * Note: The Pilot must also be accepted, as the Greenfield and Functional User Acc Test, has not contained testing of existing data / files = Participate= Follow-up

  9. Test Responsibilities and stages Infrastructure Cap Gemini Applikations Cap Gemini Int. test Unit test System test Unit test Int. test Greenfield test (2 x 5 laptops) SFR (project) Greenfield testSFR (project) System test Int. test System test Int. Test Functional User Acceptance Test (2 x 5 laptops) SFR (Business) Functional User Acceptance Test SFR (Business) System test Int. test Process test System test Int. Test Process test Implementation > Soft Go-live (10-20 users x 2)SFR Implementation > Go liveSFR Daily business Must be verified before further pilots and implementation Daily business

  10. Test Time Planning – Infrastructure IT Day2 Soft Go-live Laptop update Hard Go-live CAP Gemini Greenfield Functional UAT Soft Go-live Laptop update Hard Go-live CAP Gemini Greenfield Functional UAT Soft Go-live Hard Go-live Laptop update CAP Gemini Greenfield Functional UAT Soft Go-live Hard Go-live Laptop update CAP Gemini Greenfield Functional UAT Greenfield Functional UAT Prerequisite: Cap Gemini has completed greenfield build and Unit & int. test before SFR greenfield test starts 15/11

  11. Test Scenarios Link to Testplan

  12. Infrastructure – ESS / EUC / ECS • Dependencies: ESS <> EUC <> ECS • Unit & Infrastructure test (fase 1): To be done by Cap Gemini • Greenfield Test (fase 2): To be done by project members • Functional User Acc. Test (fase 3): To be done by business (named users located) • Detailed testplan & scripts status: In progress Deadline: 10-11-2011 • Testers located: OK, done(Deadline for locating testers: 1-11-2011) Testers approved: ApprovedLink • Link to detailed Testplan: Link

  13. Defect Log • When defects are found during testing, these defects must be logged, fixed and re-testet. Priotizing defects must be done according to this:

  14. Infrastructure – Service management (Hanne Nørgaard) • Dependencies: ESS (Enterprise System Services )EUC (End User Computing – Rune Hald) • Unit & Infrastructure test (fase 1): To be done by Cap Gemini • Greenfield Test (fase 2): To be done by project members • Functional User Acc. Test (fase 3): To be done by business (named users located) • Detailed testplan & scripts status: In progress Deadline: 10-11-2011 • Testers located: OK, done(Deadline for locating testers: 1-11-2011) Testers approved: ApprovedLink • Link to detailed Testplan: Link

  15. Infrastructure – S@SS (Jesper Drud / Åsa Otterstedt) • Dependencies: ESS (Enterprise System Services )EUC (End User Computing – Rune Hald) • Unit & Infrastructure test (fase 1): To be done by Cap Gemini • Greenfield Test (fase 2): To be done by project members • Functional User Acc. Test (fase 3): To be done by business (named users located) • Detailed testplan & scripts status: Not started Deadline: 1-12-2011 • Testers located: NO(Deadline for locating testers: 1-12-2011) Testers approved: Not approvedLink • Link to detailed Testplan: Link

  16. Applications – Desktop applikations (Jakub Turminiski) • Dependencies: Infrastructure (CapGemini)Pilot; Depending on number of users of individual application • Unit & Infrastructure test (fase 1): To be done by Cap Gemini • Greenfield Test (fase 2): To be done by project members • Functional User Acc. Test (fase 3): To be done by business (named users to be located) • Detailed testplan & scripts status: Not started Deadline: 15-1-2012 • Testers located: NO(Deadline for locating testers: 15-1-2012) Testers approved: Not approvedLink • Link to detailed Testplan: Link Some Desktop applications will be tested during the EUC-test.

  17. Applications – Middleware (Biztalk) (Wojciech Gasiorowski) • Dependencies: Infra / Server hostings / Network arrangements • Unit & Infrastructure test (fase 1): To be done by Cap Gemini • Greenfield Test (fase 2): To be done by project members • Functional User Acc. Test (fase 3): To be done by business (named users to be located) • Detailed testplan & scripts status: Not started Deadline: 15-1-2012 • Testers located: NO(Deadline for locating testers: 15-1-2012) Testers approved: Not approvedLink • Link to detailed Testplan: Link

  18. Applications – Eweb & Notes (Chris Svensson) • Dependencies: Infra / Server hostings / Network arrangements • Unit & Infrastructure test (fase 1): To be done by Cap Gemini • Greenfield Test (fase 2): To be done by project members • Functional User Acc. Test (fase 3): To be done by business (named users to be located) • Detailed testplan & scripts status: Not started Deadline: 15-1-2012 • Testers located: NO(Deadline for locating testers: 15-1-2012) Testers approved: Not approvedLink • Link to detailed Testplan: Link

  19. Applications – Horizontal Applikations (Kjetil Næssan) • Dependencies: Contiki – needs clients on desktop (inkl. citrix) Server hostings / Network arrangements / Desktop clientsPilot; Depending on number of users of individual application • Unit & Infrastructure test (fase 1): To be done by Cap Gemini • Greenfield Test (fase 2): To be done by project members • Functional User Acc. Test (fase 3): To be done by business (named users to be located) • Detailed testplan & scripts status: Not started Deadline: 15-1-2012 • Testers located: NO(Deadline for locating testers: 15-1-2012) Testers approved: Not approvedLink • Link to detailed Testplan: Link

  20. Applications – Vertical Applikations (Lauris Zoldners) • Dependencies: Server hostings / Network arrangements / Desktop clients Biztalk • Unit & Infrastructure test (fase 1): To be done by Cap Gemini • Greenfield Test (fase 2): To be done by project members • Functional User Acc. Test (fase 3): To be done by business (named users to be located) • Detailed testplan & scripts status: Not started Deadline: 15-1-2012 • Testers located: NO(Deadline for locating testers: 15-1-2012) Testers approved: Not approvedLink • Link to detailed Testplan: Link

  21. TestTool Must have: • Testpackage pr. area and user • Easy follow-up and status • Users to approve and document test directly • Possibility for defect/error handling Selected Test Tool, will be the ’troom’ Cap Gemini TeamSite, modified to handle the above requirements. Link: https://troom-x.capgemini.com/sites/SFRTransition/Shared%20Documents/Forms/AllItems.aspx

  22. Test status report N/A Manageable issues / Not completed Critical issues, requires action OK / Completed * Cap Gemini is fully responsible for Infrastructure test (fase 1) also for status reporting

  23. Outstandings • Test scenarioes and Checklists (in progress) • Detailed Testplans (in progress) • Locating test-users: Done - Greenfield (mainly project members) - Functional User AcceptanceTest (Business – approval is needed) - Pilot (Soft Go live) – Verification needed • Find common Test Tool - Done • Dates for application migr.plan (when ready for test?)

More Related