...
Validate any current Release Candidate by following the Testing Checklist Template for the specific build
Check for fixes implemented to the build that are ready for validation
Locate and input bugs to the DB as directed or AdHoc
Verify that Volunteer Management has all the resources they need to keep the volunteers at capacity
...
Expectations for Validation of Release Candidate
New Notes: See Testing & Verifying New Builds
OLD NOTES:
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. Please see the page Export of Exposure Notifications Logs for post validation data retrieval from the phones. There is a page for tracking results HERE where the previous validations have been noted and the excel version of the verification tests can be downloaded for individual testing receipts.
...