...
The purpose of this project is to add to the RBI Loyalty platform all of the features that are currently in use by BK DE (i.e. from the legacy CBA platform). At the end of the project, BK DE should be using the Loyalty Platform with no visible changes to either guests or store operators. This project does not include any requirement for POS or Kiosk providers.
Technical Test
As we develop the missing features, the RBI QA Team will run a series of tests that ensure each individual feature works as expected. If and when bugs are raised, these will be escalated to the RBI Engineering team for resolution. There is no BK DE or POS/Kiosk vendor provider involvement required as this stage.
Technical Test will cover the mobile flow only since we are not making changes to the in-store flow.
...
At this stage, we will run tests covering mobile and in-store flows 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 [link required]
...
In parallel with the migration and integration work, which requires development, we will run a separate test phase covering the mobile Loyalty flow, i.e. all of the existing loyalty RBI Loyalty platform features that already exist and therefore do not require 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.
...
Technical Test for each of the integration projects requires the POS/Kiosk vendor 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:
...
Testing would be conducted by BK DE and RBI, with assistance from each vendor POS/Kiosk provider for troubleshooting if required. To do this, we need to:
...
We expect to run one separate test phase per POS/Kiosk vendorprovider, 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:
...