Information & Technology Management Standards
User Acceptance Test Results
User Acceptance Testing (UAT) does three things for a software development project :
- They measure how compliant the system is with the business requirements.
- They expose functionality/business logic problems that unit testing and system testing have missed out since unit testing and system testing do not focus much on functionality/business logic testing.
- They provide a means of determining how “done” the system is.
In reality, by the time the UAT starts, contracts have been signed and money has been spent. So, user acceptance testing is not an "accept or reject" proposition any more. UAT is rather more about finding gaps between “how the completed system works” and “how business operational processes are performed”. Also, UAT is generally considered to be a “validation process” rather than a “verification process”. “Validation” determines if something works as intended in the user's environment and meets their needs. “Verification” determines if something has been built according to specifications.
Ministry ADE process requires that UAT testing is done on the application before the request for promotion of the whole application to Production is considered. To this effect, the Business/Client Services is required to submit the following to the Ministry along with the request for promotion :
- UAT test results or log files outlining test case name, functionality (scenario) being tested, input, expected result, actual result, pass/fail status, rectification strategy for the problems discovered, test run date and time, name of the person/role who ran the test.
- Confirmation that UAT was successful and the system has passed all the UAT test cases.
Ministry ADE process recommends preserving and storing all UAT Test cases and UAT Test data for re-running purposes.
Template |
Contact |
||
| User Acceptance Test Results | Senior Application Analyst | ||
Deliverable Reviewers
IMG Reviewers |
Other Typical Reviewers |
||
| Senior Application Analyst | Senior Business Analyst | ||
| Senior Technical Architect | |||
| Senior Database Analyst | |||
Related Deliverables
Prerequisite Deliverable |
Successor Deliverable |
||
| Unit Test Results | Go Production | ||
| System Test Results | |||
| User Acceptance Test Plan | |||
Related Standards
| User Acceptance Testing Process |

