User Acceptance Testing (UAT)

1. Why UAT matters

UAT is the bridge between system testing and going live. Without effective UAT:

• Critical business processes may not work as expected.
• Users encounter issues immediately after go‑live, eroding confidence.
• Workarounds and shadow systems emerge.
• Go‑live is delayed or fails.

2. UAT planning & preparation

Key planning steps:

• Define scope: Which processes/modules will be tested? Focus on critical business flows.
• Select participants: Business users (not just project team). Include a mix of roles and experience levels.
• Schedule: Typically 2‑4 weeks, depending on scope. Allow time for re‑testing.
• Prepare environment: Sandbox with realistic, cleansed data.
• Train UAT participants: Briefing on process, tools, defect logging.

3. Test scripts & scenarios

UAT scripts should be based on real‑world business scenarios, not just technical functions.

Scenario	Steps	Expected result
Order‑to‑cash (standard customer)	Create sales order → allocate stock → pick & pack → ship → invoice → receive payment	Inventory reduced, invoice created, AR updated
Procure‑to‑pay (rush order)	Create requisition → approve → create PO → receive goods → invoice → pay	Stock increased, AP updated, payment recorded
Month‑end close	Run depreciation → post accruals → reconcile accounts → generate P&L	Financial statements accurate

Scripts should include both happy paths and exceptions (e.g., credit limit exceeded, short shipment).

4. UAT environment & data

The UAT environment must:

• Mirror production as closely as possible (configuration, security roles).
• Contain realistic data – not too clean, not too messy. Use a copy of production data (anonymised if needed).
• Be stable – no ongoing development during UAT.
• Allow multiple users to test concurrently (to catch locking/performance issues).

5. Execution & defect management

During UAT execution:

• Users execute scripts and log results (pass/fail).
• Defects are logged with clear steps to reproduce, severity, and screenshots.

Severity	Definition	Example
Critical	Process cannot be completed; no workaround	Unable to create sales order
High	Process works but major error; workaround exists	Incorrect tax calculation (manual override possible)
Medium	Minor issue,不影响核心功能	Typo in report label
Low	Cosmetic / enhancement suggestion	Change screen layout

Critical and high defects must be fixed and re‑tested before sign‑off.

6. Sign‑off criteria

Formal sign‑off indicates the system is ready for go‑live. Typical criteria:

• All critical and high defects closed.
• Key business processes tested and passed.
• Test completion rate > 95% (e.g., 95% of scripts executed and passed).
• Business process owners have signed off.

Sign‑off is documented and presented to the steering committee.

7. Common pitfalls

• Insufficient time: UAT is rushed – never cut UAT time to meet a date.
• Wrong participants: Testers are managers, not the people who will do the work.
• Poor data: Unrealistic data hides issues.
• Scripts too technical: Users don't understand them.
• Ignoring defects: "We'll fix it after go‑live" is risky.

8. Roles & responsibilities

Role	Responsibilities
UAT Manager / Coordinator	Plan, coordinate, track progress, report status
Business Process Owners	Define scenarios, validate results, sign off
End‑Users (Testers)	Execute scripts, log defects
Functional Consultants	Support users, triage defects, fix configuration issues
Technical Team	Fix code defects, manage environment