Oracle POS - Testing Plan
Contents
- 1 Purpose
- 2 Assumptions
- 3 Phases
- 3.1 Lab Test
- 3.2 Production Test
Purpose
This document details the testing plan and phases for the Project Brief - First 100 Restaurants project.
Assumptions
No content changes, therefore test scenarios do not cover Sanity
Mobile ordering (delivery) testing is out of scope since there are no changes planned for SIDES
Integration with Deliverect is out of scope
Phases
Assumption that there will be no content changes (Sanity) required.
Lab Test
Lab Test for the Oracle integration project requires Oracle and Smoothr instances in the BK DE Lab to connect with the RBI Staging environment and test that the solution works as designed. We expect RBI and BK DE involvement to be the following:
RBI: enablement of a test environment, troubleshooting of issues throughout development and testing, fixing of issues detected on the RBI platform
BK DE STAGING
Store ID: 999996
Store address: Adenauerallee 6 Hannover Germany
BK DE: enablement of the testing Lab, creation of PLU’s in Oracle, running test cases, raising issues with the respective vendors.
During this phase, the following scenarios should be tested:
Oracle POS - In-Restaurant Testing
Production Test
After a successful Lab test, we can proceed with testing each separate integration in Production, covering the in-restaurant flows.
Testing would be conducted by BK DE and RBI, with assistance from each Oracle and Smoothr for troubleshooting if required. To do this, we need to:
Install the new version of the Oracle and Kiosk software in (at least) one restaurant for in-restaurant testing
Run the in-restaurant test cases listed here: Oracle POS - In-Restaurant Testing
Data Scenarios are not required, but are recommended for Production Test.