1 / 28

PO1C SIT1 Testing organisation and governance v. 0.1 27.04.2014

PO1C SIT1 Testing organisation and governance v. 0.1 27.04.2014. Content. 1. I ntroduction 2. Test governance 2.1 Test scope definition - SIT1 test scenarios and blocks // artefact: RU_PO1C_Test scenario design.xlsx 2.2 SIT1 test estimation // artefact: this document

neve-finley
Download Presentation

PO1C SIT1 Testing organisation and governance v. 0.1 27.04.2014

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. PO1C SIT1 Testing organisation and governancev. 0.127.04.2014

  2. Content 1. Introduction 2. Test governance 2.1 Test scope definition - SIT1 test scenarios and blocks // artefact: RU_PO1C_Test scenario design.xlsx 2.2 SIT1 test estimation // artefact: this document - test preparation estimation // artifact: RU_PO1C_Scenario preparation progress.xlsx - test execution estimation 2.3 Test scenario preparation - SIT1 test blocks specification // artefact: RU_PO1C_Test scenario block template.xlsx + How to develop test scenarios.docx - SIT1 test scenarios assembly // artefact: RU_PO1C_Test scenario template.xlsx + How to develop test scenarios.docx - SIT1 test data definition // artefact: RU_PO1C_Test data template.xlsx + How to define test data for a test scenario.docx - SIT1 test scenario preparation progress monitoring // artifact: RU_PO1C_Scenario preparation progress.xlsx 2.4 Dependencies definition - SIT1 test execution pre-conditions // artefact: SIT1 prerequisites status.xlsx - SIT1 test environment // artefact: SIT1 prerequisites status.xlsx 2.5 Test execution management - SIT1 test execution planning and resource allocation // artefact: RU_PO1C_Test execution plan and status.xlsx + How to plan SIT1 test execution? - SIT1 test execution coordination // artefact: RU_PO1C_Test execution plan and staus.xlsx + How to execute SIT1 test ? 2.6 Defect reporting // artifact: this document - Defect reporting ECC // artefact: How to report defects for ECC and legacy systems.docx - Defect reporting legacy // artefact: How to report defects for ECC and legacy systems.docx - Defect fixing process // artefact: How defects are fixed.docx 2.7 Test results reporting // artefact: Project progress dashboard.xlsx 3. Test organization 3.1 Testing resources to be allocated - Consultants and business analysts // artefact: this document 3.2 Roles and responsibilities // artefact: this document 3.3 Communication plan - SIT1 coordination + Triage // artefact: this document 4. SIT1 test success criteria// artefact: this document 4.1 Test entry criteria 4.2 Test success criteria 4.3 Test exit criteria 5. Test tools // artefact: this document

  3. 1 Introduction (1/2) The purpose of this document is to describe the approach to PO1C SIT 1 Functional and Archiving test – planning activity:

  4. 1 Introduction (2/2) This document describes: • Test Governance = test processes to achieve test success criteria, metrics and artefacts • Test Organisation = test project actors, roles and responsibilities

  5. 2.1 SIT1 test scope definition • 99 scenarios in scope for SIT1 • 126 blocks from which the scenarios will be assembled • the test will be planned out of this scope • new scenarios and blocks will be treated as additional scope The list of test scenarios and the blocks they contain can be found in artefact: RU_PO1C_Test scenario design.xlsx Path:

  6. 2.2 Test preparation estimation (1/3) • 1 step in the block = 6 min. • 121 blocks with 10 steps on average = 121 hours • 3 hours to assemble 1 scenario incl. Test data x 102 scenarios = 362 hours • review and rework 102 scenarios x 30 min. = 51 hours • total 121+362+51 +10% = 587 hours • 587 hours / 17 consultants / 50% allocation = 8,6 weeks The progress of test preparation can be found in artefact: RU_PO1C_Scenario preparation progress.xlsx Path:

  7. 2.2 Test execution estimation (2/3) • 99 scenarios x 51 blocks (in average) x 10 steps (in average) = 50490 steps • 1 step = 10 min. to execute • 50490 steps x 10 min. = 8415 hours • 8415 hours / 17 consultants 50% allocation + 3 SKU teams 50% efficiency = 21 weeks

  8. 2.2 SIT 1 test estimation total (3/3) With current resources • 8,6 weeks (test prep.) + 21 weeks (test exe) =29,6 weeks (with 50% resource allocation) • we have 10 weeks from now (1/05/2014) in project plan • Mitigation?

  9. 2.3 SIT1 Test block specification process (1/4) • Test bocks are building blocks of test scenarios • Each block describes the test steps required to test a specific functional area • Each block is in essence a small test case with steps and expected results • Test scenarios are assembled from test blocks • Blocks are developed by functional consultants • Blocks are stored in e-room 80.11 – 02 Test Blocks Library artefact:RU_PO1C_Test scenario block template. xlsx artefact:RU_PO1C_How to develop test scenarios.docx Path:

  10. 2.3 SIT1 Test scenario assembly process (2/4) • Test scenarios are assembled from blocks • Blocks are copy/pasted from the blocks excel sheet into the scenario sheet. • Blocks may be modified to fit the test scenario • Manual steps or other extra steps my be added to the scenario • Test scenarios are stored in e-room 80.11 – 04 E2E Scenario Library artefact: RU_PO1C_Test scenario template. xlsx artefact: RU_PO1C_How to develop test scenarios.docx Path:

  11. 2.3 SIT1 Test data definition process (3/4) • Test data is defined in a separate excel sheet for each scenario • Test data is defined for each scenario for each step • Ensure that you specify only test data that will be available in SIT1! • Available test data for ECC can be found in XXX • Available test data for Legacy systems can be found in XXX • NB For each test run a separate test data sheet must be created!! • Test data sheets stored in e-room 80.11 – 04 E2E Scenario Library artefact:RU_PO1C_Test data template. xlsx artefact: RU_PO1C_How to develop test scenarios.docx Path:

  12. 2.3 Test scenario preparation monitoring (4/4) • Test scenario preparation is monitored by monitoring block development and scenario development • For each block and each scenario a deadline is assigned when it should be ready • We monitor progress per team on a week by week basis The plan and progress of test preparation can be found in artefact:RU_PO1C_Test scenario design.xlsx artefact:RU_PO1C_Scenario preparation progress.xlsx Path:

  13. 2.4 SIT1 Test environments and peripherals (1/2) • ECC Environment • Q21-500 SIT1 / DR • Legacy environments • Peripherals • Printers • 1 unit Zebra label printer • 1 unit FPrint-55 check-printer (Felix) • 1 unit OKI MX-1150 (high-speed dot matrix printer) • On 15th of May I’m waiting the delivery of (I got a confirmation from procurement department today): • 1 unit Epson DFX-9000 (low-speed dot matrix printer) • And last one, by the end of May: • 1 unit OKI MX-8150 (the new version of high-speed dot matrix) • Handhelds

  14. 2.4 SIT1 Test execution pre-conditions (2/2) • SIT 1 is scoped and scenarios are developed • ECC environment is ready • ECC data are agreed and loaded • Legacy environments are ready • Legacy environments are connected to ECC • Legacy data are agreed and loaded • All peripherals are available and connected to ECC • Adequate test execution resources incl. Legacy testing are secured • Ways of working for execution, co-ordination and defect handling are agreed • All test resources have logged in to ALM and have access • ECC and legacy environments and data are verified artefact:RU_PO1C_SIT prerequisutes status.xlsx Path:

  15. 2.5 SIT1 Test execution planning (1/4) • Test execution planning and resource allocation is based on the assumption that a scenario will be tested block by block, with one tester per block. • Scenarios are listed with blocks • Each block is assigned a name given test executor (1 block = 1h to execute) • PMO assigns for each person for each week the test allocation % • E2E leads or consultants mark each RICEF in scope as critical / non critical – where critical = no workaround • Each test executor is then assigned which blocks he/she can/should test – on a daily basis based on allocation % • Test scenario execution order is based on the RICEF delivery dates, taking account critical/non critical RICEFS The execution planning can be found in artefact: RU_PO1C_Test scenario design.xlsx – “SIT1 resource planning” tab RU_PO1C_How test execution is planned.docx Path:

  16. 2.5 SIT1 Test execution and co-ordination (2/4) • Test execution during SIT1 is co-ordinated dynamically based on actual situation using a Activity-board • Each tester is assigned a number of blocks within scenarios to test. The tester find his/her blocks to test in the “Test scenario design” file in tab “SIT1 resource planning” • An Activity-board is created on a wall using deck-tape. • Each scenario is printed as a number of blocks on business-card sized queue-cards, each block consisting of scenario name + block name + block sequence within scenario on each card • The cards are places in plastic pockets attached to the wall on the left hand side of the activity board • 5 columns are created: Tester; In progress; Blocked by defect; Done w. Workaround; DONE • Pockets are also placed on the right hand side of the Board to collect the DONE blocks.

  17. 2.5 SIT1 Test execution co-ordination (3/4) • Allocation of tasks during execution is done as follows: • Testers find “their” scenarios and blocks to test in the “Test scenario design” file. • The left hand pocket holds the backlog of all tasks. A tester takes a card i.e. Block that he/she is testing from the stack and places in column “In progress”. When the block has been tested the card is placed in column DONE (using sticky tape). • If block is tested with workaround or if it is tested with non-blocking defect – the next block can be taken and the queue card is placed in corresponding column. • This signals the next tester that the next block (which now is on top of the stack in the left hand side pocket) can be tested. • If a scenario is blocked by a defect the card is placed in column Blocked by defect. • When all the queue-cards from the left hand side are taken – the scenario is tested

  18. 2.5 SIT1 Test execution co-ordination (4/4) • Testers place their queue-cards in column “DONE” to see workload. • Cards are moved from columns to right hand side pockets by test manager • The topmost cards in each left hand side pocket, are the blocks ready to be executed. Each tester can take a block and put it on his/her “In progress” column. Thus “reserving” the block to him/her. • In this way – it is possible to manage workload dynamically on a running basis based on actual situation “on the ground”. Instructions for test execution are found here: artefact: RU_PO1C_Test scenario design.xlsx – “SIT1 resource planning” tab RU_PO1C_How to execute SIT1 test.docx RU_PO1C_How SIT1 execution is co-ordinated.docx Path:

  19. 2.6 Defect reporting SAP (1/3) • 1 step in the block = 6 min. The progress of test preparation can be found in artefact: RU_PO1C_Scenario preparation progress.xlsx Path:

  20. 2.6 Defect reporting Legacy (2/3) • 1 step in the block = 6 min. The progress of test preparation can be found in artefact: RU_PO1C_Scenario preparation progress.xlsx Path:

  21. 2.6 Defect fixing process (3/3) • 1 step in the block = 6 min. The progress of test preparation can be found in artefact: RU_PO1C_Scenario preparation progress.xlsx Path:

  22. 2.7 Test result reporting (1/1) • 1 step in the block = 6 min. The progress of test preparation can be found in artefact: RU_PO1C_Scenario preparation progress.xlsx Path:

  23. 3.1 Testing resources (1/1) • 1 step in the block = 6 min. The progress of test preparation can be found in artefact: RU_PO1C_Scenario preparation progress.xlsx Path:

  24. 3.2 Roles and responsibilities (1/1) • 1 step in the block = 6 min. The progress of test preparation can be found in artefact: RU_PO1C_Scenario preparation progress.xlsx Path:

  25. 3.3 Communication plan (1/1) • 1 step in the block = 6 min. The progress of test preparation can be found in artefact: RU_PO1C_Scenario preparation progress.xlsx Path:

  26. 4.1 SIT1 entry criteria (1/1) • 1 step in the block = 6 min. The progress of test preparation can be found in artefact: RU_PO1C_Scenario preparation progress.xlsx Path:

  27. 4.2 SIT1 success criteria (1/1) • 1 step in the block = 6 min. The progress of test preparation can be found in artefact: RU_PO1C_Scenario preparation progress.xlsx Path:

  28. 4.3 SIT1 exit criteria (1/1) • 1 step in the block = 6 min. The progress of test preparation can be found in artefact: RU_PO1C_Scenario preparation progress.xlsx Path:

More Related