How to organise user acceptance testing (UAT)

Define what UAT must prove

User acceptance testing is not about retesting the whole software. It must confirm that business processes work end to end. Start by writing acceptance criteria: what must be true for the business to accept the release?

The steps of a UAT phase

• Set the scope and acceptance criteria with business owners.
• Identify testers and book their availability in advance.
• Write scenarios in business language, based on real situations.
• Prepare data and check the environment before starting.
• Run the campaign with a daily check-in on progress and defects.
• Produce a report that supports a clear decision.

Illustrative example

For a new version of a customer portal, a scenario might be: “A customer changes their address, then downloads their certificate; the certificate shows the new address.” Business users understand it and it checks several features at once.

Describe defects properly

Each defect should state the scenario, the steps, the expected result and the actual result. A shared severity scale (blocking, major, minor) avoids debates and helps decide what must be fixed before go-live.

Common mistakes

• Starting UAT while the environment is unstable.
• Leaving business testers without scenarios or support.
• Mixing change requests and defects in the same tracker.
• Deciding on go-live without criteria set at the start.

The acceptance report

The report summarises executed scenarios, open defects by severity and remaining risks. It lets decision-makers choose with full knowledge: go-live, go-live with conditions, or postpone.