Use this Acceptance Test Plan (Apple iWork Pages 25 pgs) to describe the acceptance testing process, such as the features to be tested, pass/fail criteria, approach to testing, roles and responsibilities, resource requirements and schedules. It also defines the functionality to be tested, the requirements verified by the test, test preconditions, test steps and test post-conditions.
What is user acceptance testing?
User acceptance testing, also known as UAT, determines if a piece of software meets the minimum software requirements specification. UAT determines if the software agrees with the business requirements (i.e. what business analysts have determined are important) so it can be released to users.
When is user acceptance testing performed?
After the bugs are fixed and enhancements are developed, then it is ready for UAT.
Who performs user acceptance testing?
Typically software testers, the customer, or stakeholders who perform the role of impersonating a user, that is, using the software as though they were the actual user. A non-technical definition of user acceptance testing (UAT) is when you test software so that it can be ‘accepted’ by the people you think will use your software. For example, you might create test cases that mimic the typical activities a user might perform when using your software. The tester then pretends that they’re the actual user and performs these UAT tasks. If they pass the UAT tests, then it’s once step closer to being released.