UAT test data reset

The UAT environment currently contains a large amount of obsolete or “garbage” data, which is impacting the efficiency of testing. Examiners can create controlled test data sets in UAT, but then would like the ability to be able to restore this clean, test data sets for the next round of testing.

This epic covers implementing a process for the development team to reset or restore the UAT database, so that testers can conduct their activities efficiently without interference from residual or invalid data.

Goals:

- Ensure UAT environment contains relevant and clean data for testing
- Enable internal users to conduct testing efficiently
- Define a reliable process for DB reset/back-up restore without impacting other environments

Notes:

- Decision is needed if we are going to keep the UAT or leverage Sandbox for the UAT purposes.
- Can this be useful for other purposes?
- TEST & UAT currently share the same database. Should a separate DB instance be established for UAT?

The issue names no files, tests, or entry points. Start by resolving whether UAT or Sandbox is the target and how the shared TEST/UAT database should be handled; done means a reliable reset or backup-restore process that leaves other environments unaffected.

Written by the indexing model from the issue text.