Although user acceptance testing is commonly associated with software development, it involves a variety of engineering disciplines, including physical, chemical and performance tests. Whichever area it is concerned with, the process involves confirming that the concerned product meets the users’ requirements.
The product users are the major decision makers on the acceptance or rejection of the concerned product or system. They must therefore be involved in the testing process instead of just relying on the technical experts.
It is not possible to test systems for all possible eventualities. What is important is to test the most relevant functionalities within the required timeframe. With user acceptance testing, the consumers get the opportunity to determine whether the systems deliver what they expect. They understand best what they want, a quality that professional testers may not have. The end users are the ones to shoulder the consequences of the new products and systems.
A programmer may test and conclude (rightly) that a developed system allows the recording of customer data. However, it is the business user who will actually determine whether the system can do this in a busy environment within a 2-minute telephone call. How will the recording be conducted? Will it require switching between multiple screens? Above all, will it help the business user generate money?
User acceptance testing plays an important role in risk management. Since not everything can be tested within the specified timeframe, user acceptance testing ensures that the limited resources are allocated where they will give the best impact.
This is the last step before a system is released for public use. While other tests are concerned with how systems work, user acceptance testing deals with what it does. It provides the proof that the system actually functions according to the users’ requirements.


