1 / 8

R3 INTEGRATION TEST SCENARIOS & CONDITIONS

R3 INTEGRATION TEST SCENARIOS & CONDITIONS. 9 TH August 2006. AGENDA. Background Structure of the Integration Test Scenarios and Conditions What do I have to do ? Questions. BACKGROUND. Need to create new Integration Test Scenarios and Conditions for R3 (delta to R2.1)

thuong
Download Presentation

R3 INTEGRATION TEST SCENARIOS & CONDITIONS

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. R3 INTEGRATION TEST SCENARIOS & CONDITIONS 9TH August 2006

  2. AGENDA • Background • Structure of the Integration Test Scenarios and Conditions • What do I have to do ? • Questions

  3. BACKGROUND • Need to create new Integration Test Scenarios and Conditions for R3 (delta to R2.1) • Development of accurate and full scenarios within each area will enable thorough testing of all business requirements and the ability to prove this after testing • Business sign off of all scenarios and conditions prior to scripting ensures that encompasses full process including all systems • Supports better testing • end to end process coverage • one starting point for all script development teams – no “gaps” • clear data requirements • common understanding of what condition means • Relevant Blueprint Owner and the Asset Design Team understand the solution and are the best people to provide scenario and condition definitions

  4. INTEGRATION TEST MODEL • Business Process > Requirements > Scenarios > Condition • Each business process links to a PPD and can have many requirements • Each requirement links to a number of scenarios which should provide a description of the steps involved from end to end in order to clarify the flows involved • Integration Test Conditions should provide enough information to • identify the required data characteristics for the test • identify the country/purchasing organisation/company code • identify specific assumptions relating to the testing –e.g. for promotions, only trigger promotion once per transaction • enable test teams to develop test scripts

  5. EXAMPLE • Within the FoodService Blue Print area: • Business Process: Set Up Recipe • Business Requirement: Ability to create a BOM (bill of materials) to capture ingredients, costs and inventory levels • Scenario: R3_INT_05 New Recipe Created - Recipe: create in SAP/ download to Retalix; ensure that recipe data applies correctly at site; view recipe within BOS ensuring all required details are correctly displayed • Condition: Recipe: Create 2 recipes, the first using 3 INGR items, the second using 5 INGR items. The recipes are available on the BOS, cannot be edited but can be used for production plans

  6. REQUIREMENTS • For your blueprint area: • check the set of business requirements • create integration test scenarios that will satisfy these business requirements • develop the specific conditions involving transaction details that will fulfil the scenarios and provide enough information to specify the data required some examples have been included within the template as a point of reference but will need to be expanded with a more thorough analysis • Map these requirements, scenarios and conditions into the template

  7. TEMPLATE

  8. Timeline • 9th August – Launch Meeting • 28th August – Test Conditions and Scenarios Ready for Review • 4th September – 15th September – Sign Off • 18th September – Start scripting (Integration Test Teams)

More Related