Created by Jideo Pena (Unlicensed) on Feb 22, 2023

2.1. OBJECTIVE OF UAT

  • To confirm that the application/product performs business functions as intended per business requirements.

  • To confirm that the application/product is usable from an end-user perspective (operational-ease-of-use)

  • To confirm that the application/product is compliant with regulatory and or legal requirements

  • To certify that the application/product is deemed ready for EPFS certification

2.1. EXPECTATIONS FROM UAT

  • UAT assumes that the application/product is functionally stable and that no critical functional defects will be uncovered, hence, the focus on business process validation

  • Not expected to be as extensive as System Testing

  • Final sign-off authority to provide a Go or No-Go recommendation for EPFS certification

ENTRY GATES TO UAT

  • All User Stories for EPFS are completed and signed-off

  • Completion of Selective System and Integration Testing

  • Complete of Selective Regression Testing

  • Validation undertaken against the Functional specifications

  • Staging environment and access requests all sorted out

  • UI Validations completed

  • Successful UAT sanity check is performed

  • Ensured that there are no open showstoppers / critical defects

END TO END UAT VALIDATION - OBJECTIVES

  • Application is functional and stable

UAT EXIT CRITERIA

  • Acceptance of Business Flows against Bussiness Requirements by the End Users of the System

  • All UAT defects are fixed & UAT is signed off

Attachments:

image-20220928-111719.png (image/png)