Software Testing-User Acceptance Testing

User Acceptance Testing Process
For purposes of this planning document, User Acceptance Testing has been divided into four major functions:

• Planning


• Execution


• Follow- Up


• Re-Test

a)Planning:-
The goal of a UAT(User Acceptance Testing) Plan is to identify the essential elements of the software to be tested. A User Acceptance Testing(UAT) Plan delineates high-level testing procedures and outlines the tests to be conducted.
b)Execution:-
The application will be verified / tested, using the Acceptance Test Feedback Form against the following:

• Is the degree of detail for business functionality sufficient?
  
• Do the screens completely capture business functionality?
  
• Is the business functionality content correct from the user's point of view, as recorded in the reference documents?
  
• Does the system’s business functionality perform as required?
  

Execution of the UAT Plan will be completed by performing the following tests:

1. Requirements Testing


2. Test Case Creation


3. Business Functional Requirements Testing


4. Documentation Testing


5. Verification of Online Help


6. Interface Testing

1)Requirements Testing
The purpose of the Requirements Testing is to validate that the system meets all business functional requirements. This validation shall involve Test Case creation, as well as Business Functional Requirement Testing.
2)Test Case Creation
Test case data shall be created on manual forms for data entry on crucial screens in order to cover all attributes of UAT testing. Each test case includes the steps necessary to perform the test, expected results and contains (or refers to) any data needed to perform the test and to verify it works.The UAT team will provide test cases for UAT testing.
3)Business Functional Requirements Testing
Business Functional Requirements testing information shall be created based on the Functional Requirements contained in the System Requirements Specification Document. During UAT, it is the testers’ responsibility to assure that the Business Functional Requirements Testing occurs. However, company will ensure that each Business Functional Requirement has been tested.
4)Documentation Testing
Documentation Testing ensures that the hard copy and online documentation are understandable and accurate.
5)Verification of Online Help
Online Help shall be verified by the following:
a) Corresponds to the User documentation
b) Corresponds to the screens presented in the application
c) User is directed to the appropriate help on the desired page by clicking on a page level help icon available to the users on each screen.
6)Interface Testing
Interface Testing validates that the application interfaces with external systems and databases.