Goal

To validate that a release is complete, run an end-to-end regression test for the respective platform. The output of each test should be directed as relevant to its respective database:

• → New features to add to future releases
• → Bugs or issues to be resolved in the current or future releases

Process

1. Review the overall ideal-state user flow by viewing the corresponding filter in

2. View the "Regression Test - [user]" filter in the table. The following are the functions of each data column:

   1. Parent User Story → Each Unit Test is a sub-step of a User Story. These Parent User Stories map onto the flow in the page for consistency.
   2. Test proves that... → Articulates the purpose of this Unit Test. This goal should be verified by the end of the Unit Test.
   3. Bug/Issue Status → Confirms the status of bugs or issues previously associated with this Unit Test. This provides context to what the tester should expect regarding UX.
      1. To view the bugs or issues in depth, select the desired page from the "Bug/Issue" data field inside each Unit Test.
   4. Feature Status → Confirms the status of the features associated with this Unit Test. This provides context on what functionality is currently designed to enable this Unit Test.
      1. To view the bugs or issues in depth, select the desired page from the "Feature" data field inside each Unit Test.
   5. Feature Release → Confirms the currently assigned release for the features associated with this Unit Test. This provides context to what the test should expect regarding timing.

3. Confirm the status for each test unit is "Intake."

4. Go through the full regression step for each user type.

   1. Use table to document new test users created or access a previously created test user.

5. If the test works, change status to "Confirmed (2 Eyes)" and change "Date Last Completed" to today's date.

   1. QA Lead then replicates the same tests and move to "Validated (4 Eyes)" if it also works. The purpose of validation is to apply a "4 Eyes" review lens, ensuring quality tests.

6. If the test does not work, change status to "Error Found." Include a comment detailing the error you found in the comment section below the data field for each Unit Test.

   1. Product Manager then reviews all Unit Tests under "Error Found" and produces new cards in or as appropriate.
      1. Product Manager will then review the new feature requests or bug/issue fixes with the developers to properly integrate into the Product Roadmap.
   2. Once the new cards are created, Product Manager moves Unit Tests to "Complete" for validation by the QA Lead. Follow step 4.a.