User Acceptance testing is –
- the formal testing done on the system to ensure that it satisfies the acceptance criteria before the system is put into production. [Most of the times it is done by users/clients]
- the incremental process of approving or rejecting the system during development and maintenance.
Acceptance Testing checks the system against the requirements of the user. It is done by real people using real data and real documents to ensure ease of use and functionality of systems. Users who understand the business functions run the tests as given in the acceptance test plans, including installation and Online help Hardcopies of user documentation are also being reviewed for usability and accuracy. The testers/users formally document the results of each test, and provide error reports, correction requests to the developers.
User Acceptance testing Myth – Passing the UAT acknowledges that the system is fit for use and also it acknowledges the process of development was adequate.
Reality: “Passing the acceptance tests does not necessarily mean the software is acceptable. That’s just the first hurdle to acceptance.” – via @the Three Amigos – Better Software Magazine [NOVEMBER/DECEMBER 2011]
Now a days we are using Agile and Incremental software development models. So Acceptance testing should be the ongoing activity. It needs to involved in the development process and approximate correction need to be made whenever it fails the acceptance criteria.
Ongoing Software Acceptance Testing enables:
- Early detection of software problem.
- Early consideration of user needs during software development.
- Ensure user are involved in system and acceptance criteria.
- Decision involved based on the results.