User Acceptance Testing is a critical step in the System Development Life Cycle. It is still a mystery for some, and an absolute failure for others.
All you think you know about UAT is wrong
- UAT is often confused with Bug Hunting or System Testing for the majority of the time.
- It is important to realize that User Acceptance Testing (UAT) is a type o system and business objective validation. This is done by end-users and then signed off by project owners.
- User Acceptance Testing’s purpose is to validate the use cases. This is a test of specific daily operations in an end user’s life and their ability to complete their job function according to Standard Operating Procedures (SOPs).
Most common errors in UAT:
- Confusion between UAT Testing and System Testing- System testing is done by the Consultant or Developer in a Development Environment. In a UAT Environment, end-users perform user acceptance testing.
- Confusion of UAT Testing and Bug Hunts User acceptance testing is used to validate business requirements. It should be about the day-to-day function of your job, not testing every menu item, feature, enhancement, or looking for bugs. While you might discover some along the journey, that is not the goal.
- Confusion between UAT Testing and Enhancement Requests UAT’s goal to deliver business functionality is based on the scope and business requirements. This has been approved by the owner, project sponsor, and other decision-makers. There’s a place and time for enhancements. Typically, there is a follow-up v1.1 phase to address any must-have enhancements.
- Cases Not for Use You may think that you have use cases when you have system test cases and training documentation. Re-examine your use cases to see if they pass the test. One question: Does this use case describe a business job function or is it just a general overview? Is it useful for system testing or training? Oder something else?
- A UAT Testing Tool is not required excel will not work, sorry. This is not real-time and collaborative. It will double or triple the budget, while your team’s morale plummets. A proper administrator is essential. Software testing tool that allows you to pass or fail tests with enough supporting data. You can find many on the market or have your own.
We have now covered the basics. Here are some best practices to ensure UAT success:
- Support Structure- Create a support system and define roles and responsibilities.
- Daily Stand Up Calls Coordinated by the decision-maker and UAT Test Lead, with the UAT Test Team. This call covers the following:
- UAT Decision Tree- Create a UAT decision tree, which is what happens if and what to do next.
- Check out the Test Results Questions, unanticipated behaviour, workarounds, comments from testers
- Maintenance of Test Cases Identify new test cases and make necessary changes to existing ones
- Scribe- Designate someone to take notes and track any “nice-to-haves”, “parking lot items”, or “knowledge articles” that are needed. This function is usually performed by the Knowledge Manager/Trainer.
- Regular UAT calls between the Consultant/Developer and the Decision Maker to discuss the progress, the test results, and the UAT remediation scope.