...
At this stage, we will run tests covering mobile and the in-store flows flow directly in the Production environment. We don’t believe that a test in Staging is required, since Technical Test will be performed in Staging already. To do this, we need to:
Identify specific RBI and BK DE users
Enable the Loyalty platform for these users only
Run these test cases: Milestone 7 - Product Test [Rollout]
We recommend scheduling the mobile and in-store testing separately, since in-store testing requires splitting testing across features that can be tested without needing to complete an order (for example: upsells, marketing tiles, personalizd offers) an those that require physical presence in a selected store.
...
Projects 3-7. Integrate POS and Kiosk with Loyalty platform
Loyalty Test
In parallel with the migration and integration work, we will run a separate test phase covering the mobile Loyalty flow, i.e. all of the RBI Loyalty platform features that already exist and therefore do not need to wait for software development. This test is useful to give BK DE an initial view of how the Loyalty platform works from a guest perspective, although it will not yet include features in scope for the migration project such as open offers or marketing tiles.
To run this test, we need to:
...
Identify specific RBI and BK DE users
...
Loyalty platform
...
...
Run these test cases [link required]
Technical Test
Technical Test for each of the integration projects requires the POS/Kiosk provider to connect with the RBI Staging and BK DE Lab environments and test that their solution works as designed. We expect RBI and BK DE involvement to be the following:
...
Each vendor is free to determine the scope of their own technical testing phase. RBI recommends running that vendors run at least the test cases documented here. [link required]
Production Test
Once the Technical Test phase is completed: Toshiba - Production Test [In-Store]
Lab Test
After each vendor confirms that their Technical Test has been successful, we recommend that BK DE tests that the integration works as expected using the Lab environment.
| Info |
|---|
This test phase is optional, since it’s possible to skip it and test directly in Production. In our experience, there is benefit in running this test phase since it typically highlights a large number of issues, which are quicker to fix and deploy to Lab/Staging than to Production. |
Project 8. Loyalty Enablement
With all the POS and Kiosk integrations developed, the next step is to guarantee that the Loyalty content and features are working as expected.
Content Test
After the Loyalty content has been created in Staging (rewards and any new offers) these have to be promoted to Production and tested there. This phase should be executed by BK DE (Content Agency) and the RBI QA team, in parallel.
See test cases here: Milestone 1 - Content Test
Production Test (Online)
In parallel with the migration and integration work, we will run a separate test phase covering the online (iOS, Android, Web) Loyalty flow, i.e. all of the RBI Loyalty platform features that already exist and therefore do not need to wait for software development.
This test phase should only happen after Content Test.
To run this phase, we need to:
Identify specific RBI and BK DE users
Enable the Loyalty platform for these users only
Run these test cases: Milestone 2 - Production Testing [Online]
Production Test (In-Store)
As each vendor completes their integration development, and after a successful Lab test, we can proceed with testing each separate integration in Production, covering the mobile and in-store flows. We don’t believe that a test in Staging is required, since Technical Test will be performed in Staging already.
Testing would be conducted by BK DE and RBI, with assistance from each POS/Kiosk provider for troubleshooting if required. To do this, we need to:
...
We expect to run one separate test phase per POS/Kiosk provider, to be executed as each integration becomes ready (i.e. we don’t have to wait for all integrations to be developed to start testing each).
Other
Maybe specific call-outs for:
...
.
...