...

Welcome

The concept of the Path Check Covid Defense/Aware app is for health and safety of the public. It is an open source product with a git repository that is HERE. The website is HERE and you can learn more about the goals of the app and people behind it on that page.

...

Currently the team uses Jira for tracking of both bugs as well as tracking stories. The current format is the Kanban lanes, but that may change (or may have already been changed). However, to note, the fixed issues will appear in the ON BUILD READY FOR QA TEST lane when they are ready for validation.

...

Basic Functionality of the Product

This app revolves around the GAEN (Google Apple Exposure Notification) format for informing the user if they have been within a 6ft range (bluetooth range) of a person that has received a positive test for COVID-19 within the last 14 days.

...

For testing purposes, the developers have included a debug menu in the Settings page. The “EN Debug Menu” has the ability to simulate an exposure, which will yield a randomized exposure notification. To note: this data does not leave the device and does not need a validation code for verification. One of the other main uses of these tools is to verify that Local Diagnosis Keys have been generated (which can take up to an hour).

...

Focus of Primary Directives

Currently, Path Check works towards a *weekly Sprint for Release Candidate for Heath Authorities. This may have changed, however, at the time of writing here are the main focuses QA needs to keep in mind during the day.

...

*team format is to have a build ready to test by Monday, validated on Tuesday and given a greenlight/redlight by Wednesday if possible. At the time of writing the Sprint Review occurs on Thursday, and the next weeks build is kicked off on Friday.

...

Expectations for Validation of Release Candidate

The Validation tests can be located HERE. The Verification General Test should be completed first, at the bottom it includes the End-To-End validation which requires AT LEAST TWO (2) phones and upwards of 12-24 hours for completion of the test. The End-to-End is also separated out for easy usage. There is also a separate page for the Interface Check validation steps and another page for the Upgrade Testing. I would recommend that the Interface Check be completed second, followed by the Upgrade Testing third, then the End-to-End Validation last. This is only a suggestion of best time management, your mileage may vary.