Document Provision UAT testing process
Problem
The UAT testing process for new products is a repeatable process, but it is not well defined and documented. As new products are being prepared for release we want to ensure that the process is as uniform as possible and known issues with generating or executing tests cases are identified and made easier for smoother quicker testing.
Proposal
We should document within the Provision section of the handbook what our current UAT testing process is. From both a prospective of this is what the process is and how you run through it that would help an engineer unfamiliar with provisioning or customers dot run through the process of validating a change. As well as from the a theoretical perspective of what we're testing, and why those tests help us produce working end application features.
Result
One or more pages are created in the handbook under the PATH TBD hierarchy that define the current provision testing process in both theory and practice.
Next steps (if any)
Follow up with https://gitlab.com/gitlab-org/fulfillment-meta/-/issues/1420+, to identify the elements of the process that cause difficulties and slow downs for developers.