Executing User Acceptance Testing and Logging Defects

Keep this: job aid

UAT tester card

• Before step 1: system and client, own user and roles, build level, test data, current test case.
• Missing dependency = blocked. Ran and differed = failed. Matches expected = passed.
• Record facts: message type and number, document numbers, values, statuses.
• Record a failure before any workaround.
• Evidence: document flow with statuses plus journal entry against expected values.
• Store evidence with the test run; name files by case, step, content and document number; mask personal data.
• Defect: summary, environment, steps, data, expected with source, actual, evidence, impact.
• Severity is impact; priority is urgency.
• Retest: confirm the fix is imported, use fresh data, check downstream and sibling scenarios.
• Report daily: progress, defects, blockers, risks, next steps.