Downloaded 505 times
Uploaded byThomas Martin
User Acceptance Testing (Uat)
User acceptance testing (UAT) validates that a system meets user needs by determining if it fulfills business requirements, as opposed to quality assurance (QA) which verifies that a system meets its specifications. An effective UAT involves creating test cases from business requirements and processes, using a combination of requirements-based, process-based, and data-driven approaches, and systematically recording the test plan execution and results.
In this document
Powered by AI
Introduction to testing emphasizing it’s more than basic methods, detailing UAT for validation versus QA for verification.
How to create test cases from requirements and business processes, stressing a mixed approach for best practices.
Outline of testing parameters including functionality, inputs, and outputs, highlighting the importance of a structured test plan.
More Related Content
Similar to User Acceptance Testing (Uat)
User Acceptance Testing (Uat)
- 1. It’s not justhunt and peck
- 2. Measures compliance withbusiness requirements A means to determine if the system is "done” QA & UAT are not the same UAT = Validation = It meets user needs QA = Verification = It meets a specification
- 3. Requirements + BusinessProcess = Test Cases Test Cases + Test Plan + Execution = UAT
- 4. Requirements-based test casesBased on business requirements Business process-based test cases Based on workflow or business process Data-driven test cases Based on script that drive data through the system Best Practice: A combination of all three approaches
- 5. Functionality being testedInputs Expected results Actual results Go/No-Go status + Rectification strategy Test date and time Tester
- 6. Early and oftenPost unit and system testing Have test data to support the test plan . Create a chronological test plan. Don’t start testing without a test plan. Follow the tests in the test plan. Did I mention having a test plan ?