UAT goals
User Acceptance Testing should confirm that the product works for real users in realistic workflows.
Core test groups
Recommended UAT coverage includes owner and admin setup, submitter workflow, reviewer workflow, evidence enforcement, restricted visibility, search and queues, notifications, dashboard correctness.
Typical UAT structure
Each test should include persona, prerequisites, steps, expected outcomes, pass/fail result, and notes.
Example scenario: Submitter creates and submits a high-risk change
- Log in as the submitter
- Create a draft
- Complete guided intake
- Generate Coordination Plan
- Generate Revenue Impact Report
- Apply approvers and evidence
- Submit for review
Expected outcomes: readiness becomes satisfied, report and plan appear, review status updates, approval request becomes visible to the assigned reviewer.
Recommendation
Use seeded personas and sample changes for UAT so every run is comparable and easier to debug.