About User Acceptance Tests

Prior to releasing a new piece of software, in-depth testing is required to ensure that the new product functions as intended. No matter how thorough a programmer's search for bugs and errors on the back-end, a few usability issues will almost certainly slip through the cracks. To discover these errors and fix them prior to a product's launch, many engineers and product developers take advantage of user acceptance testing (UAT).

Function

In general, acceptance testing is the process of systematically testing a series of conditions or cases on an engineered product. The process can be computerized, with a series of tests intended to mimic the expected user environment. However, in the case of user acceptance testing, actual people are tasked to test the product. Usually, this is done by knowledgeable Subject Matter Experts (SMEs) of the engineered product. Through trial and error, these experts systematically check the functionality of all possible inputs and outputs offered by the software.

Effects

The SMEs are usually given a test script to follows. These scripts may feature specific input directions or may simply ask the tester to complete a required task. Once each task is completed, results of the process are compared with the intended results. If the intended results are achieved, then the task is said to be successfully completed.

Benefits

User acceptance testing is one of the final stages of any software development program. It is often implemented following computerized acceptance testing because it more effectively replicates the real-world user environment. As such, if a product passes UAT, it can generally be assumed that the product will deliver satisfactory results to the final consumer or client.

Considerations

Though primarily used for software development, user acceptance testing is frequently used for other purposes. These purposes are generally related to engineered products such as engine components, other mechanical parts and chemicals. In each application, the goal is the same---to identify and fix any errors in design prior to releasing the item to the end-user.

Expert Insight

User acceptance testing is just one of many testing methods. A few alternatives include:
Alpha testing: software products are tested by internal staff
Beta testing: software products are tested by a selected group of end users
Contract acceptance testing: testing a system to ensure it meets all obligations as expressed in a written contract
Operational acceptance testing: testing a system's processes to ensure maintenance procedures (updates, patches, etc.) can be effectively implemented.