Acceptance testing

A release readiness test for validating whether or not the technical solution satisfies the usability and operability requirements as specified in the business requirements specification.
Final check-point before signing-off of a product.
Acceptance Testing is also Called:
User Acceptance Testing (UAT)
Client/Customer Acceptance Testing (CAT)
Operational Acceptance Testing (OAT)
Contract & Regulation Testing (CRT)
Alpha and Beta Testing (ABT)

A release readiness test for validating whether or not the technical solution satisfies the usability and operability requirements as specified in the business requirements specification.
Final check-point before signing-off of a product.
Acceptance Testing is also Called:
User Acceptance Testing (UAT)
Client/Customer Acceptance Testing (CAT)
Operational Acceptance Testing (OAT)
Contract & Regulation Testing (CRT)
Alpha and Beta Testing (ABT)


A release readiness test for validating whether or not the technical solution satisfies the usability and operability requirements as specified in the business requirements specification.
Final check-point before signing-off of a product.
Acceptance Testing is also Called:
User Acceptance Testing (UAT)
Client/Customer Acceptance Testing (CAT)
Operational Acceptance Testing (OAT)
Contract & Regulation Testing (CRT)
Alpha and Beta Testing (ABT)

UAT is kind of black box testing. Prepare the below steps to test a product:
Planning the UAT
Identifying Schedule of UAT
Designing the test cases
Finding manual/automated test cases
Preparing the test suites
Identifying resources to execute test suites
Executing test suites
Documenting the defects
Resolving the Issues/Defects/Bugs
Getting signoff