To catch 95% of prod issues during deployment testing process.
To catch user facing issues in production environments in regression tests and #triage them accordingly.
A deployment test completed twice by the Operations Workstream during each release process:
A full regression test performed once a day by an Operations Workstream contributor.
Operations prioritizes blocking bugs, supporting engineers, and efficiency in the processes already in place over chasing non-blocking bugs for a ‘perfected’ release.
Feature Release Testing Guides
https://shapeshiftdao.gitbook.io/getting-started/general-information/release
Operations has a representative in each release. This representative is responsible for organizing the testing during the deployment, as well as final sign off for Operations in testing both develop and production. The Operations Lead is also responsible for following the outlined release process above, and for filling out the Releases Table below during the release.