It’s not just hunt and peck

Measures compliance with business 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

Requirements + Business Process = Test Cases

Test Cases + Test Plan + Execution = UAT

Requirements-based test cases Based 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

Functionality being tested Inputs Expected results Actual results Go/No-Go status + Rectification

strategy Test date and time Tester

Early and often Post 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?