Development Support and User Acceptance12% of the exam
Planning and running user acceptance testing
How the BA plans UAT (testers, scripts, schedule, sandbox and test data, defect process, sign-off), runs it (triaging defects, enhancements and usability issues, retesting, reporting progress), and gives decision makers the facts for a go/no-go call backed by written sign-off.
Support and validate user acceptance testing (UAT) to ensure the solution meets the requirements.
~8 min read · 19 practice questions ·
What the exam expects
- Explain what UAT is and when it happens: end-user testing in a sandbox, after the technology team's testing, as the last stage before go-live.
- Plan UAT: real end users and subject matter experts as testers, scripts traced to acceptance criteria, schedule and status cadence, defect process, a sandbox with representative data, and sign-off.
- Run UAT: record results, triage each finding as a defect, an enhancement or a usability issue, retest fixes with regression checks, and escalate coverage gaps.
- Support the go/no-go decision with facts and obtain written sign-off, keeping the record as auditable evidence.
Key terms:
- UAT: testing by end users for approval before production release.
- Test script: a scenario broken into steps whose outcome is pass or fail.
- Defect: delivered behaviour that fails an agreed acceptance criterion.
- Go/no-go: the release decision made from UAT results and business readiness.
- Sign-off: the business stakeholders' written, official acceptance.
Key facts
Definition
- Detail
- End-user testing in a sandbox or test environment
Timing
- Detail
- Last stage before go-live, after the technology team's testing
Testers
- Detail
- End users and subject matter experts
Sign-off
- Detail
- Written, official business sign-off before go-live
Partial Copy sandbox
- Detail
- Metadata plus a template-defined sample of production data; for UAT
Full sandbox
- Detail
- Replica of production, all data
Developer sandbox
- Detail
- Configuration only; create your own test data
Test priority
- Detail
- High-value and high-usage processes first
Cost of bugs
- Detail
- Fixing in test costs significantly less than in production
- When does UAT happen in the delivery sequence?
- Why must UAT testers be end users or subject matter experts?
- Which sandbox type does Salesforce name for QA tasks such as UAT and includes a sample of production data?
- Why is a defect found late in UAT still a good outcome?
- What must the BA obtain before deployment?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Business Analyst pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 22 lessons of the Business Analyst guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (19 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams