DC773

Archive for the ‘user acceptance testing’ Category

A functional trial performed on a system before it is commercially released to the market or delivered to the client is called user acceptance testing. This is designed to replicate the anticipated true-to-life use of the application in order to ensure that what the customer or end user receives is fully functional and meets their expectations and requirements.

In a way, user acceptance testing is the last opportunity the end users or customers have to make sure that the system delivered to them is what they asked for. One the user acceptance test is complete, the project team expects that the customer will either formally approve the system or point out any issues and problems that need to be addressed and resolved. Hence, unlike all the other tests done to the system during the earlier stage of its development, user acceptance testing can be considered the customer’s responsibility. Of course, unless the end users are very knowledgeable in testing techniques and technology, they will still need the participation and guidance of the IT team.

In some cases, depending on how rigorous your other tests were performed, user acceptance testing may not always be necessary. If the customers and end-users participated in system testing such as in requirements tests and in usability tests, they may not need to perform a formal user acceptance testing. However, user acceptance testing will probably be required for the user or customer to give their final approval for the system before it is transitioned to production.