Contents
Table of Contents | ||
---|---|---|
|
...
# | Scenarios | Test Steps | Test Result | Notes |
---|---|---|---|---|
1 | The guest signs-in and it is navigating in the app and his phone has the battery level > 30%, so no special offer will be triggered. |
| PASS | |
2 | The guest not signs-in and it is navigating in the app and his phone has the battery level <= 30% |
| PASS 25/10: Akhil Mohammed can you please re-test this scenario and add a video? Thank you | Offer is available for NOT signed In User and User able to navigate to Sign up screen as expected |
3 | The guest signs-in and it is navigating in the app and his phone has the battery level <= 30%. The guest will receive an In-App message or the guest can access directly the Offers Page. The guest does not redeem the offer. The guest charges their phone and the offer will disappear from the Offers Page. |
| PASS | In-App message are not received. We tested navigating directly to Offers section. |
4 | The guest signs-in and it is navigating in the app and his phone has the battery level <= 30%. The guest will receive an In-App message or the guest can access directly the Offers Page. The guest redeem the offer. In the same day, the guest charges his phone to 100% and opens the app again. The special offer will be not show in the app because the guest already redeem the offer in the same day. |
| FAIL | User able to see the offer even after redeem in restaurant. |
5 | The guest signs-in, opens the app, navigating and move to another app. BK app is running in the background and the battery level is still checking by our app each 10 minutes for iOS and 15 minutes for Android. The guest has the battery level > 30%, so no local notification will be triggered and no special offer will be available on the Offers Page. |
| PASS | |
7 | The guest signs-in, opens the app, navigating and move to another app. BK app is running in the background and the battery level is still checking by our app each 10 minutes for iOS and 15 minutes for Android. The guest has the battery level <= 30%. The local notification will be triggered and when the guest clicks on the notification, we will redirect him to the Offers Page. The special offer will be available on the Offers Page. The guest does not redeem the offer. The guest charges their phone and the offer will disappear from the Offers Page. |
| FAIL |
|
8 | The guest signs-in, opens the app, navigating and move to another app. BK app is running in the background and the battery level is still checking by our app each 10 minutes for iOS and 15 minutes for Android. The guest has the battery level <= 30%. The local notification will be triggered and when the guest clicks on the notification, we will redirect him to the Offers Page. The special offer will be available on the Offers Page. The guest redeem the offer. In the same day, the guest charges his phone to 100%, the local notification will be not triggered and no special offer will be available on the Offers Page. |
| FAIL | User able to see the offer even after redeem in restaurant. |
5. Local notification is not triggered - Core FE investigation
Date 12th Nov 2024
After 2 weeks of testing, App Staging and QA, we noticed the background task was not triggered the local notification which means the some how the iOS and Android system is blocking it.
After further investigation from Core FE Team, the binaries and the configuration were reviewed and both of them are correct. There are some system level issues with scheduling the background task
Unfortunately there's not much we can investigate about the system level battery optimizations as mentioned above the risks. The battery optimizations feature on iOS and Android is killing our background job and because of that, the local notification is not triggering and then the offer will be not available.
Date 13th Nov 2024
The background task is running every 5 minutes and we will change the interval to 30min/1 hour to test if the iOS and Android will still keep kill the background task.
Core FE team will change and generate a new App Shell in QA to restart the tests.
https://ionic.io/blog/create-background-tasks-in-ionic-with-capacitor