These test cases need to be conducted in every BK ES Loyalty Migration Phase (Phase 0-3)

Phase 0

Scenarios

Steps	Expected results (Homeria/Airtouch app)	Expected results (RBI APIs)
Place Delivery or Pickup Order- only earn points BEFORE the data dump	Loyalty Points of User will increase User sees in the App updated loyalty balance	No action
AFTER the data dump login to Homeria/Airtouch App	The user’s loyalty point balance is the same as what it was before the data dump	RBI APIs show same loyalty point balance as what is shown to the user in the Homeria/Airtouch app
A new user signs up during the data dump Warning: these new users will not be in RBI DB. Therefore, we recommend doing the migration at the time/day where there is less sign ups (e.g. 6am Monday)	User gets created	User does not exist in RBI platforms

Steps	Expected results (Homeria/Airtouch app)	Expected results (RBI APIs)
New user creates an account	User information is saved in SessionM after it is saved in RBI User information that is saved in RBI Loyalty shows in the Homeria Website	Calls the Create User endpoint Website calls Get User Details from RBI, using the RBI Loyalty ID as input. This endpoint will retrieve loyalty points balance and loyalty tier
User inputs address, chooses menu items and offers (rewards is deactivated) and goes to checkout	User sees checkout and payment information	Call `Create Transaction` using the RBI Loyalty ID
User pays for the order (Earn only)	User sees increased loyalty point balance in the app Homeria/Airtouch	Call `Transaction Update` with an empty basket and set the transaction to `CLAIMED`

Steps	Expected results (Homeria/Airtouch app)	Expected results (RBI APIs)
User logs back in to account	User information that is saved in RBI Loyalty shows in the Homeria Website	Website calls Get User Details from RBI, using the RBI Loyalty ID as input. This endpoint will retrieve loyalty points balance and loyalty tier
User inputs address, chooses menu items and offers (rewards is deactivated) and goes to checkout	User sees checkout and payment information	Call `Create Transaction` using the RBI Loyalty ID
User pays for the order (Earn only)	User sees increased loyalty point balance in the app New user point balance is saved in Session M and Homeria	Call `Transaction Update` with an empty basket and set the transaction to `CLAIMED`

Steps	Expected results (Homeria/Airtouch app)	Expected results (RBI APIs)
User logs back in to account	User information that is saved in RBI Loyalty shows in the Homeria Website	Website calls Get User Details from RBI, using the RBI Loyalty ID as input. This endpoint will retrieve loyalty points balance and loyalty tier
User inputs address, chooses menu items and offers (rewards is deactivated) and goes to checkout	User sees checkout and payment information	Call `Create Transaction` using the RBI Loyalty ID
User pays for the order (Earn only)	User sees increased loyalty point balance in the app and new Tier New user point balance is saved in Session M and Homeria	Call `Transaction Update` with an empty basket and set the transaction to `CLAIMED`

Steps	Expected results (Homeria/Airtouch app)	Expected results (RBI APIs)
User logs in website and is identified	N
User logs in app and is identified
User identifies at kiosk
User identifies at POS
User places an order for delivery - card
User places an order for delivery - cash
User places an order for pick up - dine in - card
User places an order for pick up - take away - card
User places an order for pick up - table service - card
User places an order for pick up - dine in - cash
User places an order for pick up - take away - cash
User places an order for pick up - table service - cash
Delivery order is cancelled by restaurant in tablet
Delivery order is cancelled by restaurant in driver app
Delivery order is refunded by Homeria admin tool
Pickup order is cancelled by user (30min before)
Pickup order is cancelled at POS as customer does not show up?
Pickup order is refunded by Homeria admin tool