UAT | Learn IT Fundamentals with Teacher Pochi

Key points

UAT (User Acceptance Test) is the final check where the client or actual end users confirm the system genuinely works for their business.
Where the earlier test phases were run from the development side's perspective, UAT is run from the "user's" perspective.
Passing UAT means the system is finally ready to move on to release into production.

What UAT is

UAT (User Acceptance Test) is called "acceptance testing." Unit test, integration test, comprehensive test, and system test were all mainly run by the development team to confirm "was this built according to the requirements?" In UAT, the client or actual end users themselves confirm, "can we really use this in our own work?"

🔑 Everyday exampleIt's similar to the "trial period" you get before buying a new appliance. Even if it's already passed the manufacturer's quality inspection (the development side's testing), you only feel confident continuing to use it once you've tried it in your own daily life and decided "yes, this works for me."

How it differs from the earlier test phases

What sets UAT apart most from the other test phases is "who" checks it and "what standard" they use.

Development team
Was it built according to requirements?

The perspective shifts

Client / users
Does it genuinely work for our business?

What UAT checks

✅ Business fit Can it be used without friction in the actual business workflow?

🖱️ Usability Is the operation intuitive and easy to understand?

📋 Business requirement fulfillment Was what was originally requested actually delivered?

What happens if UAT is skipped

Even if technical quality has already been confirmed through the system test, skipping UAT carries the risk of releasing a system where "the features are all there, but it doesn't actually fit how the business works."

UAT performedMismatches with the business can be found and fixed before release

UAT skippedProblems like "hard to use" or "doesn't fit our workflow" only surface after release

What comes after UAT

Once the client and users give their approval in UAT, the system finally moves on to release into the production environment. This is the stage where the business and system requirements defined earlier in the upstream process finally take shape as something people can actually use.

Summary

Unlike the earlier tests, which were run from the development side's perspective, UAT is the final check confirming that the client and users can genuinely use the system in their own work. Getting approval here is the last gate before release.