Copyright 2018 Blueprint Consulting, LLC. All rights reserved

Purpose

UAT directly involves the intended users of the software. Implementing UAT is accomplished by making software available for a free beta trial on the internet or through an in-house testing team comprised of actual software users.

Benefits of UAT

A general path to conducting an effective UAT is as follows:


Determine which test cases to use for UAT: Test cases are designed to cover all the functional scenarios of the software in real-world usage. They are intended to merely the test process for the testers.

Select the UAT team: Ideally, the team will consist of actual end users, along with some software testers or business analysts.


Execute test cases: The UAT team executes the designed test cases, along with some ad-hoc testing. Software defects are logged within a defect tracking tool, such as JIRA.


Development fixes defects: Developers respond to the problems found during each iteration of UAT and modify the code to make the resolve each bug.


UAT Sign-off: When all defects are resolved, the UAT team formally accepts (or recommends acceptance to the project manager) the software application as developed. The approval shows that the application meets user requirements and is deployable.


Ensuring the software as designed will meet the needs and expectations of the intended end users of the application.

User Acceptance Testing

User Acceptance Testing (UAT) is designed to ensure that the end users of an application are satisfied that the newly created or re-designed app works as expected at the end user level.  Functional effectiveness, and mainly, the ease of use and ability to navigate the application are prime considerations during this phase.  

How UAT works

The primary benefits of conducting a thorough User Acceptance test before deployment are:


  • Increased end-user/client satisfaction. Satisfaction is reflected in a higher coincidence that the software will work how and when they need it to perform their roles and responsibilities.  There shouldn't be any "showstopper" software defects when the software is implemented into the production environment.
  • The quality criteria of the product are defined in the early phase of development/implementation.   
  • The software development project team reduces pressure on itself during the implementation and risks of post-implementation fixes in the "live"/production environment. 
  • Stakeholders use the information gathered through UAT to understand the target audience‚Äôs needs better.