User acceptance testing

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Webagogue (talk | contribs) at 04:54, 24 June 2005 (Explained UAT is more a simulation and verification than a test to fix bugs.). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Jump to navigation Jump to search

User acceptance testing (UAT) is one of the final stages of a software project and will often be performed before a new system is accepted by the customer.

Users of the system will perform these tests which ideally are derived from the User Requirements Specification, to which the system should conform.

A formal test plan will be drawn up and a range of severity levels devised. The focus in this type of testing is less on simple problems (spelling mistakes, cosmetic problems) and show stoppers (major problems like the software crashing, software will not run etc.). These issues should have been worked out during unit testing and integration testing. Rather, the focus is on a final verification of the business function and flow of the system. The test scripts will be grouped such that they emulate real-world usage of the system. The idea is that if the software works as intended and without issues during a simulation of normal use, it will work just the same in production.

Results of these tests will allow both the customers and the developers to be confident that the system will work as intended.

Retrieved from "https://en.wikipedia.org/w/index.php?title=User_acceptance_testing&oldid=15732160"