Skip to main content
 

Project Management Methodology and Acceptance Test

User Acceptance Test Overview

User Acceptance Test (UAT) or End user Testing is used to ensure the future everyday users of the delivered product accept what is being delivered;

  • They will need a run through of the system;
  • Their first run should be a scripted run through of the functionality;
  • Once they are comfortable they should have free reign

User Acceptance Testing - What Is It

User Acceptance Testing it is checking that the real users of the system (not the developers, or project team members), can operate the system to achieve the business process. The User Acceptance Testing is the always performed near the end of the project when the final software looks as you anticipate it will, and before Performance Testing incase any changes are requested by the users.

User Acceptance Testing - What Should Be Tested

User Acceptance testing should involve real life business process scenario, and should try to include tests which attempt to make the process fail so you can find out if there any any issues before going live with new software.

User Acceptance Sign-Off

User Acceptance Test should be used to allow the ultimate users of the system to accept that it is going to work for them.

User Acceptance Testing Checklists


Click here to access a list of User Acceptance Test considerations

Click here to read more on our Project Management Methodology

Comments HistoryBe a pioneer and write the first comment.

Note: Current average rating of  based on  reviews and ratings. (1-Low, 5-High)

Note: Comments and ratings help this site get better; if you see something missing, see something wrong, have a question, or want to suggest something to improve then comment below and join the dialogue;

Comments