UAT

User Acceptance Testing

In plain language

The last test of new software, done by the people who will use it, before it goes live.

The metaphor

Like a test drive before buying the car: the people who will drive it every day confirm it does what was promised.

Going deeper

How it works

Real users run real tasks from their normal day.
They sign off or list fixes needed.
It comes after the developers' own testing.
The sign-off is often tied to final payment.

What can go wrong (example scenario)

A clinic was moving to a new booking system. During acceptance testing, front-desk staff found it could not handle double bookings, and the fix was made before go-live.

How WILDCARD handles it

Projects covers rollouts and migrations, including the acceptance steps before a switch.

In practice

Front-desk staff try the new booking system on ten typical appointments.
An owner signs off a new website after checking the contact form.
A team tests invoicing in the new accounting tool before cutover.

A question owners ask

Who should do the acceptance testing?

The people who will use the software every day, not only the manager who bought it.

Where WILDCARD handles this

🏗️

Projects

Templated or custom projects
Migrations, moves, rollouts
Quoted per project

Start with Projects

Related terms

Something here sounds like your problem?

Every WILDCARD card exists to solve one named problem. Find yours.

Pick your problem →