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 10 Next »

Welcome!

Hello and thank you for offering to help test the PathCheck app for the Google-Apple Exposure Network (GAEN) corona virus response. This document should have everything you need to get started, but if you are blocked, please reach out to [test lead/ volunteer coordinator/slack channel?] for assistance.

Issues to notify PathCheck of while testing

If you encounter any of these during your time testing, please [*** bug report channel? ***]

  • Crashes, error messages, or other unexpected behavior. (Please be as specific as possible) 

  • If you never receive a notification 

  • If the expected results don’t match what you expect (e.g. calendar does not have a day highlighted, wrong day highlighted, etc.) 

Device Setup

iOS [13.5 or later only]

If you don’t already have TestFlight installed on your devices, you’ll need to first install it using the following instructions. If you already have TestFlight installed, skip to the “Start Testing step.

Installing TestFlight

  1. Load the TestFlight “join” URL on the device(s) you intend to use for testing: https://testflight.apple.com/join/byXkRxFs [<- Guam specific link]. You should see:

  2. Select the “View in App Store” button to load the App Store and follow the normal steps to download and install TestFlight.

  3. Once TestFlight is installed, return to your browser and select “Start Testing” under “Join the Beta” to launch TestFlight.

Installing the Beta App

  1. Select “Install” to install the beta app (app names will vary by specific location being tested).

  2. Once the app is installed, select “Open” to launch the app

  3. TestFlight will walk you through a short introduction:

  4. Select “Start Testing” to begin testing. You should see a welcome screen:

Updating the Beta App

Future updated app builds will appear in TestFlight and trigger new email reminders and push notifications to download and continue testing: 

Android [TBD]

End to End Exposure Notification Test Steps

[Requires: 2+ phones w/sim cards, verification code]

This test will walk you through the end to end (e2e) main exposure notification (EN) flow, including on-boarding and diagnosis verification code submission.

Test Setup & Prerequisites

  1. Complete Device Setup steps for at least two mobile devices [with sim cards & Bluetooth enabled]

  2. Have access to at least 1 valid verification code for a positive diagnosis (this should be provided by a test lead)

  3. Go through the on-boarding flow and exposure notifications and proximity tracing are enabled on each phone

  4. Return to your devices respective home screens and leave each app running in the background for at least an hour. This is necessary for your phone to start generating keys that will be required later on.

Triggering an Exposure Notification

  1. After your test phones have had sufficient time to passively download an exposure key, move them into proximity (2m/6ft) with each other (if they weren’t already) for at least 15 minutes

  2. On one phone, open the app and select “Report positive test result”

  3. Advance to the next screen and enter the 8 digit verification code (Setup step 2)
    Note: verification codes are only valid for 1 hour from the time of their generation

  4. Select the ‘Share’ button on the pop-up that asks you to share your device’s random IDs. 

  5. Select the ‘I understand and consent’ button on the subsequent screen. 

  6. Select the ‘Done’ button to return to the Home screen. 

  7. Check the other non-positive phone for an exposure notification - this process may take up to 24 hours

  8. Tapping the notification will take you into the app, where the circular “exposure” icon (2nd from the left) will take you to the Exposure History which should be populated with any test exposures we prompted

Proximity Test (Simulated ENs)

[Requires: 2+ phones w/sim cards?]

This test is a truncated version of the e2e EN test above meant to test proximity tracing and the showing of simulated Exposure Notifications without a verification code.

Test Setup & Prerequisites

  • Same as e2e EN test above, except no verification code is required

Triggering a Simulated Exposure Notification

  1. After your test phones have had sufficient time to passively download an exposure key, move them into proximity (2m/6ft) with each other (if they weren’t already) for at least 15 minutes

  2. Select the More menu (three dots icon) and then the EN Debug Menu

  3. Select Simulate Exposure on at least one phone

  4.  You should see a popup debug message and receive a push notification of a possible 

    COVID-19 exposure.

  5. Click OK to dismiss the debug message, and click the notification to return to the app.

  6. Tapping the notification will take you into the app, where the circular “exposure” icon (2nd from the left) will take you to the Exposure History which should be populated with the test exposure

One Phone Tests [TBD]

[Requires: 1 phone w/sim cards?]

 


 

  • No labels