Scribd
Upload
503 views10 pages

User Acceptance Testing

User Acceptance Testing (UAT) is the final phase of testing performed by end users to verify that a software system meets business requirements before it is deployed to production. UAT tests end-to-end business processes and validates that any requirements changes have been addressed. It occurs after unit, integration, and system testing, using production-like test data setup. The goal of UAT is to ensure the software is accepted by clients and end users prior to release.

Uploaded by

mdrazi10
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
503 views10 pages

User Acceptance Testing

User Acceptance Testing (UAT) is the final phase of testing performed by end users to verify that a software system meets business requirements before it is deployed to production. UAT tests end-to-end business processes and validates that any requirements changes have been addressed. It occurs after unit, integration, and system testing, using production-like test data setup. The goal of UAT is to ensure the software is accepted by clients and end users prior to release.

Uploaded by

mdrazi10
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 10

User Acceptance Testing

What is UAT ?

 User Acceptance Testing (UAT) is a type of testing performed by the end user
or the client to verify/accept the software system before moving the software
application to the production environment. UAT is done in the final phase of
testing after functional, integration and system testing is done.
Purpose of UAT
 The main Purpose of UAT is to validate end to end business flow.
 It does not focus on cosmetic errors, spelling mistakes or system testing.
 User Acceptance Testing is carried out in a separate testing environment with production-like data setup.
 It is kind of black box testing where two or more end-users will be involved.
 UAT is performed by –
 Client
 End users
Need of User Acceptance Testing

 Need of User Acceptance Testing arises once software has undergone Unit,
Integration and System testing because developers might have built software
based on requirements document by their own understanding and further
required changes during development may not be effectively communicated
to them, so for testing whether the final product is accepted by client/end-
user, user acceptance testing is needed.
 Developers code software based on requirements document which is their
“own” understanding of the requirements and may not actually be what the
client needs from the software.
 Requirements changes during the course of the project may not be
communicated effectively to the developers.
Prerequisites of User Acceptance
Testing
 Following are the entry criteria for User Acceptance Testing:
 Business Requirements must be available.
 Application Code should be fully developed
 Unit Testing, Integration Testing & System Testing should be completed
 No Showstoppers, High, Medium defects in System Integration Test Phase –
 Only Cosmetic error is acceptable before UAT
 Regression Testing should be completed with no major defects
 All the reported defects should be fixed and tested before UAT
 Traceability matrix for all testing should be completed
 UAT Environment must be ready
 Sign off mail or communication from System Testing Team that the system is ready for UAT
execution
How to Execute UAT Tests

 UAT is done by the intended users of the system or software. This type of
Software Testing usually happens at the client location which is known as Beta
Testing. Once Entry criteria for UAT are satisfied, following are the tasks need
to be performed by the testers:
UAT Process
Conti…

 Analysis of Business Requirements


 Creation of UAT test plan
 Identify Test Scenarios
 Create UAT Test Cases
 Preparation of Test Data(Production like Data)
 Run the Test cases
 Record the Results
 Confirm business objectives

You might also like