Start with real working scenarios.
User acceptance testing, or UAT, asks whether the workflow does what the business needs. Define the starting information, the steps a person follows, and the result they should get.
Platform guide G03
Test the work your team depends on.
Use automated user acceptance testing to check how an app supports real business work before a change reaches the wider team.
Read the guide3 min read
Check the change before rolloutG03
Alex · Your virtual learning guide
A little guidance.
A clearer next step.
Follow the reading, unpack the idea, and put it into practice. At your pace.
What this guide helps you decide
Acceptance checks tied to a real business outcome.
Make the checks repeatable.
Automate the checks that need to run again as an app changes. Include the normal path and the situations that matter to your team, such as incomplete information or an interrupted handoff.
Keep acceptance with the business.
A completed test is evidence for a release decision. The process owner still needs to review the results, assess exceptions, and decide whether the change is ready for the people using it.
Illustrative test plan
Improve a customer intake process.
Before adding a new requirement to intake, check both complete and incomplete submissions against the expected result.
- 01
Define the result
Describe what a complete intake should pass to the next team.
- 02
Check the exception
Check what happens when required information is missing.
- 03
Accept the change
Review the results with the process owner before rollout.
Use this example to shape your own process with the people responsible for the work.
Take it into your next working session
Prepare a useful acceptance test
Work through these decisions with your team. Use the lesson when you are ready to put the guide into practice.
A working checklist for this visit.
Put the idea to work
Turn requirements into UAT checks
Build a small acceptance checklist and work through the decisions behind a useful test.
