Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Contents

Project 2. Migrate BK DE to new Loyalty platform

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 provider involvement required.

Technical Test will cover the mobile flow only since we are not making changes to the in-store flow.

Production Test

Once the testing above has been completed, all of the features in scope will be available in the Loyalty platform, however they will not be enabled for any BK DE guest.

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

We recommend scheduling the mobile and in-store testing separately, since in-store testing requires physical presence in a selected store.

Content Test

Once the software is ready, we can then migrate all of the existing offers from CBA (legacy) to the Loyalty Platform. To do this, we need to:

  • Run a script that migrates all the existing offers from CBA (legacy) to Loyalty (Staging environment)

  • Promote all the existing offers to Production (there is no need to test in Staging since these offers are hidden from guests)

  • QA all offers. This should be done in parallel by the content agency and the RBI QA team

  • Fix any issues found

Once the content is confirmed to work as expected, we can switch the Loyalty platform on for all guests and finalise this project.

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

  • Enable the Loyalty platform for these users only

  • 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:

  • RBI: enablement of a test environment, creation of offers in Sanity, troubleshooting of issues throughout development and testing

  • BK DE: enablement of the testing Lab, creation of PLU’s

Each vendor is free to determine the scope of their own technical testing phase. RBI recommends running at least the test cases documented here. [link required]

Production Test

Once the Technical Test phase is completed, 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:

  • Identify specific RBI and BK DE users

  • Enable the Loyalty platform for these users only

  • Install the new version of the POS and Kiosk software in (at least) one store for in-store testing

  • Run these test cases [link required]

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:

  • Testing cash payments for all the Kiosk providers. Ideally Toshiba would be ready when we test each kiosk, otherwise we can do a separate test at the end just for cash payments

  • Do we need to test Personalised Offers separately?

  • No labels