...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Build Validated for Release Candidate?
- Validated by QA Lead
- Released Live
Summary:
This is a checklist for the QA lead to run through the tests of the app and make sure they don’t miss any important steps
Test Started:
...
Current available HAs:
PR, Guam, MN, LA
| Info |
|---|
iOS -Device used: iPhone 7 HA used: “Guam” Android -Device used: Samsung Galaxy S7 HA used: “LA” |
...
ONBOARDING / BLUETOOTH / LOCATION
Goal: a user can download the app and make it to the core features.
# | Instruction | Check (iOS) | Check (Android) |
1 | Install App |
|
|
2 | Proceed through onboarding wizard (5 screens) |
|
|
3 | Open "How we protect your privacy" |
|
|
4 | Try to Activate Exposure Notifications |
|
|
5 | Enable Notification |
|
|
6 | Access Home Page |
|
|
8 | *Enable Location (*only necessary on older Android OS's) |
| |
9 | Verify Exposure Detection is ON |
|
|
...
MANUALLY DETECT EXPOSURES
Goal: a user can manually prompt the app to check for exposures
# | Instruction | Check (iOS) | Check (Android) |
1 | Select the "Exposures" tab from the bottom menu |
|
|
2 | Click the "Check for exposures" button |
|
|
--
EXPOSURE HISTORY
Goal: a user can access their exposure history populated with exposures
# | Instruction | Check (iOS) | Check (Android) |
1 | In Settings, Use the EN Debug menu to simulate 1 or more exposures |
|
|
2 | Navigate to Exposure History |
|
|
3 | Tap on an exposure |
|
|
...
GAEN (Google Apple Exposure Notifications) Permissions
Goal: an onboarded user can enable required permissions as expected.
# | Instruction | Check (iOS) | Check (Android) |
* | Disable Exposure Notifications (device OS), Enable |
|
|
* | Disable Location (if applicable*) on device / Re-enable |
|
...
VERIFICATION CODE & KEY SUBMISSION
Goal: an onboarded user can submit a verification code as expected.
# | Instruction | Check (iOS) | Check (Android) |
1 | Generate verification code* |
|
|
2 | Access App, select Report Result area |
|
|
3 | Enter verification code |
|
|
4 | "Next" > "Share" > "I understand and consent" |
|
|
* | Offline: disable devices network connectivity and execute above test |
|
|
* | Invalid Code: Submit a non-valid verification code |
|
|
...
--
MANUALLY DELETE APP DATA
Goal: a user can manually delete their data stored by the app
# | Instruction | Check (iOS) | Check (Android) |
1 | Access the Settings page |
|
|
2 | Press "Delete My Data" |
|
|
3 | Press "Delete My Data" red banner |
|
|
4 | Press “Confirm” on pop-up |
|
|
--
APP UPDATE
Goal: a user can update the app and verify that simulated exposure is still shown
# | Instruction | Check (iOS) | Check (Android) |
1 | Install build 1.0.x (older) from AppCenter |
|
|
2 | Navigate to debug menu and tap "simulate exposure" |
|
|
3 | Navigate to Exposure history screen and view exposure |
|
|
4 | Download Staging build 1.0.y (newer) from AppCenter |
|
|
5 | Return to updated app’s “Exposure History” Tab |
|
|
...
GAEN EXPOSURE NOTIFICATION (END-TO-END VERIFICATION)
Goal: a user can receive an exposure notification and see it on the exposure history.
NOTE: Two (or more) phones running app w/ Exposure Notifications ON required.
...
# | Instruction | Check (iOS) | Check (Android) |
1 | Let phone sit for AT LEAST 1 hour (app in background) |
|
|
2 | Move phone to within 6 ft of another testing phone (at least 15 minutes) |
|
|
3 | "Report positive test result" > "Start" > enter code > share keys |
| |
4 | Wait (up to 24 hours) |
| |
5 | (On 2nd phone) Open Exposure History |
|
...