UAB GAEN Testing Strategy

Owned by Ben St John
Last updated: Feb 15, 2021
3 min read

This is the baseline test for the UAB (University of Alabama at Birmingham) Health Authority. This same test applies to any other future mobile applications that will use a similar SMS verification code layer for the APHL server. Currently the only HA (health authority) using this strategy is UAB.

 

Starting a fresh End to End test (attempting to get an exposure notification to appear on the device).

  • Make sure to have at least 2 devices in a “test group” that are near one another (within 6 feet of each other).

  • Make sure there is a designated United States phone number for this test. Once the phone number has been used for a test, that phone number cannot be used again. For spinning up new temporary phone numbers, we have been using Twilio. See instructions for spinning up new phone numbers here: ____

  • Once you have a phone number ready for the test, make sure to get it “allow listed” by the correct team. At the time of writing this, Rajesh from the UAB team will add the phone number. In the #pathcheck-uab channel on Slack, message @rpillai with the phone number and request that the phone number be allow listed. DO NOT PROCEED WITH THE SMS VERIFICATION STEPS WITHOUT THIS COMPLETED.

  • Download the latest version of the app in AppCenter

    • If you are using an iOS device, make sure to have your UDID added into the build. See other documentation for this.

    • If you are using an Android device, make sure to download the PRODUCTION version of the app on AppCenter. If you don’t have access to download it, you may need to adjust your accounts access on AppCenter.

    • NOTE: if you don’t use the production version of the Android application you will not be able to enter in a phone number for the SMS verification, halting the testing process.

  • Once the apps have been downloaded on the various devices, make sure to go through the entire onboarding process and turn on Exposure Notifications on the device and make sure ‘Alabama’ is set to the Active Region within your Exposure Notification settings.

  • As soon as the devices are “live” exchanging keys with one another, create a new Ticket on the “QA Jira Board” - https://pathcheck.atlassian.net/jira/software/projects/QA/boards/42 where you log the setup of your “test group”, the date you began running the test, and other important details.

  • Sample Ticket Below

  • From the time of starting the test, make sure to wait 48hrs before doing anything else.

  • During this period, make sure to NEVER check local diagnosis keys on the mobile app settings in the debug menu. When checking these keys, a bug is introduced into the app and halts the ability to submit.

  • After 24 hours have passed, wait an additional hour (25 total) then select one of the devices to be the “Covid positive” device, document in Jira, and enter in the designated phone number into the app to receive an SMS code.

  • Twilio should redirect the verification code to your personal number, submit this code into the app to send up the positive verification code and initiate Exposure Notifications on the other devices. Make sure to document this code within the Jira ticket.

  • In the #pathcheck-uab channel on Slack, message @rpillai with the verification code that was entered into the device and request a “log for this OTP - [insert verification code]”. Copy the entire log provided to you, and paste it into the comments of the respective Jira ticket.

  • At this point, if all has gone well with no errors, the other devices in the “test group” should be ready to receive an exposure notification. Wait up to 48 hours for an Exposure Notification to come through, and communicate with the development team in #c_tech with questions or issues.

  • Once an EN comes through, log it on the Jira ticket - move the Jira ticket to the “verified by QA” column, and notify the #c_tech team