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

Author: Diarmid Mackenzie

Last updated by: Diarmid Mackenzie, Saturday 19 April, 5am EDT

Testing Activity


Safe Paths Android: v1.0 now delivered to tha App Store. This release is not without issues, and there will be a number of quick follow-up releases over the coming days.

  • See V1.0 App Store Release Candidate - Quality Assessment for the input I gave on this release - thanks to everyone who provided input

  • Vedha Kannan continues to manage volunteers working with the Test Case library in PractiTest.

  • PM will be laying out a pla for the next release & roadmap - should be opportunities for Testers to get involved in the Scrum team to discuss user storeis etc. in advance of delivery of a final build into Test.

Safe Paths iOS: We have still not got through Beta App Review, so we are limited in our TestFLight distribution.

  • Eran Kinsbruner has provided a private tenant for iOS testing. Contact Jonathon Wright if you would like access. Perfecto.io - Remote Mobile Testing (Automated & Manual)

  • Jonathan Wright can repackage / resign the IPA file to deploy to any iOS devices (just need peoples device IDs (uid) and apple ids). Onboarding (TiP)

  • Luca Dusi team of ~20 testers are testing iOS at the moment,

Safe Places

  • Adam Leon Smith has been developing an Test Plan:  Safe Places < this includes notes on how to contribute

  • We have had delays on the PQA Test team, that were going to work on this.

  • The PQA Test team may still come through, but in the meantime, there is a definite need for testers to work on Safe Places testing, as per Adam’s Test Plan - please help if you can!

Safe Paths Automation


Safe Places Automation 

  • Team from PQA Test has not started yet.


Test Data / Location Data

  • Adam Leon Smith is looking at a number of solutions for Test Data

    • His own Google location history.  5 years of data rebased into 86 different versions of March 2020.  He has tools to do this manipulation if you want to (see the test plan doc) 

      • If you are using your own long-term location history for testing, be mindful of privacy concerns, and keep the data to yourself (do not share with the project) unless you have explicit agreement otherwise.

    • He has a ML contact who can use this as seed data to generate many more similar trails.

      • Huw Price previously solved this problem for smart cities project, Jonathan Wright has reached out for the 5billion historical journeys previously generated (GPX format).

  • We have a lead on a tech that allows a user to program alternate GPS coordinates into their phone, to simulate being in different locations.  Could be a powerful enabler, as testers will be able to use test data from anywhere in the world.

    • Jonathon Wright is qualifying this opportunity. Working with Eran Kinsbruner around using the same stack we used to test smart city mobile apps (https://youtu.be/wuQt97rTa1Y)

  • Test Data / Mock HAs for Automation.  Problem that will need solving. Probably give to PQA Test as part of their Automation mission -

  • Diarmid is looking with Dev at whether we can bypass the complexities of the Ap’s interfaces on location data by isolating the relevant components of the App in a pure software harness, and simply feeding location data in directly. Test Strategy for Location Data Filtering / Presentation Algorithms. Would be keen to find technical testers keen to work on this - needs some programmind / data skills.

  • Security / Privacy

    • Privacy & Security - Current Status
      Pritesh Patel + colleagues from BioConnect are experts in this space & starting to pull together an overall strategy, based on the previous bullet as a starting point.

    • PM + Dev are now engaged with the importance of Privacy, and the need for a cleear plan to close existing gaps.

    • Dev are working with Salesforce, who have offered to

    • Adam Leon Smith has raised a feature request for a brief architectural deployment/security note on this for Safe Places

Real world testing

  • This is challenging in lockdown, but vitally important, and now urgent as we will soon have prospects doing their own real-rold testing & we need to be ahead of the prblems they are going to find.

  • See; 25 April 2020 - Real-world GPS test #1 for an example of some testing that has shown up a bunch of significant concerns. We need a more global spread on this, so anyone who would be able to conduct similar testing, please do so.

Testing in Production


User / UX Testing

  • This is being managed by the UX group,

  • Ali Raizin is lead, please contact here if you;d like to help.

Haiti customer testing

  • We have an opportunity to work closely with a lead prospect in Hait, to define what testing they should do, and support them through it.

  • An important opportunity to shape our first customer deployment & ensure we

  • Nobody yet assigned to this - volunteers please contact Diarmid Mackenzie

Testing Community support

  • May Moorefield has been reaching out to people to try to understand how we can better support people who want to contribute, but are finding it hard to do so.

  • We will also have a “Lean Coffee” discussion meeting, with an open agenda, o this theme TODAY (Saturday) at 12pm EDT. I hope people are able to join.

Key impediments for the team

These include a raised date (baselined at 4/19), to provide some accountability in terms of resolving impediments quickly.

  1. (4/19) Too many gaps in documentation of requirements, and detailed product behaviour

    1. Diarmid hoping to drive something here, but anyone else who could take this on would be amazing.
      (Diarmid making slow progress with PM here, on varous threads)

  2. (4/19) No available domain expert for Contact Tracing

    1. Kyle is working on a contact through Alina

    2. Is one enough?  Or do we need more?

  3. (4/19) No signatory to make a contract with Applause

    1. Du Tri will take it forward for Partnership to action - have pushed again to try to make this happen

  4. (4/19) No clear path for escalation of very high-level issues identified in Test - e.g. Privacy / Security concerns

    1. Diarmid now has a comms channel established with Sam, when needed, and improved organization of the PM team means it’s much clearer where to go with specific issues.

  5. (4/19) PractiTest not yet embedded as a tool.

    1. Limited test cases documented in PractiTest

    2. No clear patterns for using PractiTest for more exploratory forms of testing and for overall Requirements Tracing - not clear whether or not we want to invest in this, much of this is happening in Confluence today, and that may be good enough.

  6. (4/19) No current process for raising reqs/spec issues uncovered in Test

    1. We’ve been asked not to file these in GitHub issues.

    2. We believe we’ll be moving to Jira, but not quite ready yet

    3. We need to update guidance for testers.

  7. (4/19) Broad set of resources now available in Confluence, but it’s still proving difficult for even experienced testers to engage with this project, when they first arrive. We are tryng to get a better understanding of what else can we do. Are further resources neeed? What? Do we need to run in a much more explicitly directed manner? May Moorefield outreach + Lean Coffee session will hopefully provide some answers.

  8. ??? what else - please add your impediments here

Who owns resolving impediments?  We all do! I (Diarmid) am very happy to brainstorm about forward paths on any of these - reach out on Slack.

Other useful docs:


Testing Resources


  • No labels