User Acceptance Testing
Acceptance testing: Formal testing conducted to enable a user, customer, or other authorized entity to determine whether to accept a system or component
User Acceptance Testing (UAT) is performed by Users or on behalf of the users to ensure that the
Software functions in accordance with the Business Requirement Document. UAT focuses on the
following aspects:
Acceptance testing: Formal testing conducted to enable a user, customer, or other authorized entity to determine whether to accept a system or component
User Acceptance Testing (UAT) is performed by Users or on behalf of the users to ensure that the
Software functions in accordance with the Business Requirement Document. UAT focuses on the
following aspects:
- All functional requirements are satisfied
- All performance requirements are achieved
- Other requirements like transportability, compatibility, error recovery etc. are satisfied.
- Acceptance criteria specified by the user is met.
Entry Criteria
- SIT must be completed.
- Availability of stable Test Environment with the latest version of the Application.
- Test Cases prepared by the testing team to be reviewed and signed-off by the Project coordinator (AGM-Male).
- All User IDs requested by the testing team to be created and made available to the testing team one week prior to start of testing.
Exit Criteria
All Test Scenarios/conditions would be executed and reasons will be provided for untested conditions arising out of the following situations
All Test Scenarios/conditions would be executed and reasons will be provided for untested conditions arising out of the following situations
- Non -Availability of the Functionality
- Deferred to the Future Release
- All Defects Reported are in the ‘Closed’ or ‘Deferred’ status. The client team should sign off the ‘Deferred’ defects.
