...
The mobile app for test must be built and distributed using the Apple Developer account of an HD with GAEN entitlements
Until we get Apple approval for an open Beta (still a work in progress), this limits us to a total of 25 testers per HD (including any HD staff who want to test)
Testing of customizations will need to be done in the context of HD accounts. This may prove difficult if we want to test customizations that are not of direct interest to that HD: building good relationships so that these partners are willing to support us is key.
On both iOS and Android, we are very limited in terms of our ability to control which Bluetooth Random IDs get stored on the phone. There is no way to populate these programmatically - the only way to do so is to have a real Bluetooth device nearby, broadcasting keys. This makes it very hard to set up a phone with a realistic set of Bluetooth Random IDs that a phone might pick up over a 14 day period.
Testing Exposure Notifications e2e can be very slow because it can take a full day for the necessary client-server interactions to get an EN to a phone, after a set of infected keys are shared. The fact that all this function is handled opaquely by the OS means that there is no easy way around this. This means that test cases take a very long (and unpredictable) elapsed time to complete.
Testing Priorities
At the start of testing, we went through a process with Bob Mallon, where we
...
Who in PathCheck is worrying about general GAEN/BT deficiencies. Can we get a research project kicked off on this?
Can we develop tools that can simulate many phones being near another phone over Bluetooth (are there tools from Trinity College Dublin we can re-use here)?
Can we find a way to reduce the elapsed time required for an EN test (currently ~a day due to client-server GAEN protocol delays)?
Privacy & Security - need clear overall plan
Customization: what’s the plan for MN & can we deliver? What’s the plan for “productized” customization for the next wave of deployments after MN?
Analytics: what are we doing & can we deliver?
What’s the schedule for languages? Presumably depends on copy changes? And gets scuppered by HDs modifying text - do we have a plan for that?
What’s coming fast on the heels of MN that we need to watch out for?
Security: how can we get BugCrowd engaged with GAEN?
What is the risk of Accessibility and/or Security becoming hard blockers at MN or other HAs?
What are our requirements on HD tuning of controls of risk parameters?