User Acceptance Test (UAT) Checklist for IT Projects

UAT Checklist

Project Team Awareness / Preparations
Has the project team been made aware of its role in advising on changes to business processes and procedures?
Has the project team been made aware of its role in providing support for all testing issues?
Has the project team been made aware of its role in tracking and managing website bugs?
Team Preparations
Has the UAT team been defined?
Does the UAT team understand its responsibility in executing the test cases and ensuring that the final outcomes of the tests are satisfactory?
Has the team been told about its role and responsibility in ensuring that all test case input sources and output results are documented?
Has the team agreed that the test cases provides comprehensive and effective coverage of all aspects of the functionality of the application?
Has the team been told about its role in documenting bugs/problems and working with the project team to resolve problems identified during testing?
Does the team understand the responsibilities and required actions for each category of the problem identified during testing?
Has the team been made aware of its role in accepting the results on behalf of the relevant user population?
Does the UAT team understand that it must recognise any changes necessary to existing processes and
take a lead role in ensuring that the changes are made and communicated to other users?
Does the UAT team understand its role in verifying performance on business critical functions?
Does the UAT team understand its role in confirming the integrity of data?
Does the UAT team understand its role in assessing system final production readiness?
Test Preparation
Has the plan for acceptance testing been created?
Have all possible system functions been described?
Is all input data available that is required for testing?
Has acceptance criteria been defined on which the completion of the acceptance test will be judged?
Have all user specific constraints been considered?
Has the testing procedure been defined?
Have test cases been created to discover contradictions between the software product and the requirements?
Have test cases been created to review whether timing constraints are met by the system?
Test Execution and Evaluation
We’re all steps of the test run documented?
Was the acceptance test performed according to the test plan?
Did the users review the test results?
Are the services provided by the system in compliance with user requirements?
We’re all defect documented?
We’re all identified defects and issues resolved?
Did the users judge acceptability in accordance with the predetermined criteria?
Did each user sign off on output?