Platform

Solutions

Resources

Platform

Solutions

Resources

Platform

Solutions

Resources

Blog

Salesforce UAT: How to Plan, Run and Sign Off

Rishabh Kumar

Published on

Salesforce Test Automation
eBook CTA Background
RECOMMENDED RESOURCES

The Ultimate Enterprise Guide To Agentic Testing

AI agents can write, fix and triage your tests at scale. See how to use them in QA while keeping people in control of everything that ships.

Get the eBook →

Enterprise guide to agentic testing
eBook CTA Background
RECOMMENDED RESOURCES

The Ultimate Enterprise Guide To Agentic Testing

AI agents can write, fix and triage your tests at scale. See how to use them in QA while keeping people in control of everything that ships.

Get the eBook →

Enterprise guide to agentic testing
eBook CTA Background
RECOMMENDED RESOURCES
Enterprise guide to agentic testing

The Ultimate Enterprise Guide To Agentic Testing

AI agents can write, fix and triage your tests at scale. See how to use them in QA while keeping people in control of everything that ships.

Get the eBook →

eBook CTA Background
RECOMMENDED RESOURCES

The Ultimate Enterprise Guide To Agentic Testing

AI agents can write, fix and triage your tests at scale. See how to use them in QA while keeping people in control of everything that ships.

Get the eBook →

Enterprise guide to agentic testing

Table of contents

Lorem ipsum

Lorem ipsum

Lorem ipsum

Lorem ipsum

Lorem ipsum

A Salesforce release can pass every functional test and still fail the people who use it. Opportunities move through the right stages, but sales reps need six clicks too many. Approvals route correctly, but to managers who left last quarter. Reports run, but don't answer the questions leadership actually asks.

Salesforce user acceptance testing (UAT) is where you catch that. It's the final check before go-live, where the people who'll use Salesforce every day confirm it supports how they really work.

In this guide, we'll cover what Salesforce UAT is, what makes it different, why it often goes wrong, and a step-by-step way to plan, run and sign it off. You'll also find templates for UAT scenarios and sign-off, a checklist, and how to automate UAT without taking it out of business users' hands.



What is Salesforce UAT?

Salesforce UAT is testing done by business users, not the QA team, to confirm that Salesforce supports their real processes before it goes live.

QA checks that Salesforce was built to the specification. UAT checks that the specification actually solves the business problem.

Functional Testing Asks

UAT Asks

Does the opportunity move through each stage correctly?

Can our sales team actually close deals this way?

Does the validation rule fire?

Does the rule stop bad data without blocking real deals?

Does the approval route to a manager?

Does it route to the right manager, in our actual hierarchy?

Does the report run?

Does the report answer the questions we need answered?

For the basics of UAT in general, beyond Salesforce, see our guide to user acceptance testing.



Salesforce UAT vs Other Testing

Testing Type

Who Does It

What It Checks

Unit testing (Apex)

Developers

Individual pieces of code work

System and integration testing

QA team

Salesforce works to spec, and connects properly to other systems

Regression testing

QA team, usually automated

Changes haven't broken anything that used to work

UAT

Business users

Salesforce supports how people really work, and is ready for go-live



What Makes Salesforce UAT Different

What's Different

Why It Matters

Business users lead it

Sales managers, service reps and analysts run the tests, but they're busy and rarely technical

It needs realistic data

Users can't judge Salesforce with a handful of clean test records. They need realistic accounts, pipelines and case volumes

It must reflect real work

Real sales cycles have exceptions and workarounds that formal requirements miss

It crosses systems

Most processes involve ERP, marketing, e-commerce or data platforms, and users care about the whole outcome

Time is tight

UAT usually happens in the last few weeks before go-live, when schedules are already stretched

It ends in a business decision

Business owners, not QA, decide whether Salesforce is ready



Why Salesforce UAT Often Goes Wrong

Problem

What Happens

Business users aren't really involved

UAT is handed to proxies, so sign-off doesn't reflect real business needs

Scenarios are too tidy

Tests written by technical teams follow ideal paths, so UAT passes and real-world gaps show up after go-live

Test data is too simple

Clean, minimal data hides problems that appear with real volumes and messy records

Time pressure cuts scope

Important processes get less testing, and business owners sign off with doubts

Integrations are skipped

Data doesn't sync, or downstream processes don't trigger, and nobody finds out until production

Sign-off becomes a formality

People sign the acceptance form without really checking, which covers the project but doesn't protect the business



How to Plan Salesforce UAT


  1. Define the Scope

  • Focus on business processes, not features: Instead of "check the Account object saves data", test "can sales manage customer relationships properly?"

  • Cover journeys from start to finish, like a lead through to a closed deal and post-sale follow-up, or a case from creation to resolution and customer feedback.

  • Test for each role: Reps, managers, service agents and executives all use Salesforce differently.

  • Include integrations: Can sales see ERP data for quotes? Do cases trigger field service? Does revenue data sync to finance?

  • Check speed and ease of use: Are pages fast enough? Can people finish tasks without confusion?


  1. Agree Who Does What

Role

What They Do in UAT

Business process owners

Set acceptance criteria, approve the UAT plan and make the final go or no-go decision

Power users

Run most of the scenarios, and judge whether Salesforce helps or gets in the way

Subject matter experts

Check complex scenarios and edge cases, like compliance steps in financial services

Executive sponsors

Review the results and approve go-live

QA facilitators

Prepare environments and data, support users and record results, so users can focus on checking

Admins and developers

Answer questions, fix issues and log enhancement requests


  1. Write the UAT Plan

Section

What to Include

Processes in scope

For example, lead to opportunity, quoting, contracts, orders, case management, knowledge, campaigns and reports

Priority

Rank by revenue impact, volume, regulation and how much adoption depends on it

Scenarios

Normal paths, exceptions and edge cases, and integration scenarios for each process

Acceptance criteria

Specific, measurable outcomes, not "it works well enough"

People and time

Who's testing what, and how much of their time it will take

Environment and data

Which sandbox, and what data it needs

Timeline

Start and end dates, checkpoints and the sign-off date

Issue process

How issues are logged, prioritised, fixed and retested

A good acceptance criterion is specific.

For example: "A sales rep can create an opportunity, add products, generate a quote and submit it for approval in under five minutes, without help."


  1. Set Entry and Exit Criteria

Ready to Start UAT

Ready to Sign Off

System and integration testing are complete

All high-priority scenarios have passed

The UAT sandbox is set up and frozen

No open critical issues, or an agreed plan for any that remain

Test data is loaded

Every in-scope process has been tested by the right roles

Users have access matching their real roles

Business process owners have formally signed off

Testers know what to test and how to log issues

Known issues and workarounds are documented


  1. Prepare the Sandbox and Data

What to Do

Why

Use a dedicated UAT sandbox

A Full sandbox gives the most realistic set-up and data. A Partial Copy sandbox can work for smaller projects

Freeze changes during UAT

Changing configuration mid-test makes results unreliable

Load realistic data

Use masked production data or realistic synthetic data, with real volumes, relationships and some imperfect records

Make connected systems available

End-to-end scenarios need the other systems to be up and configured

Give users their real permissions

Test with the same profiles, permission sets and sharing rules people will have in production, not admin access

Note any performance differences

If the sandbox is slower than production, tell testers, so they don't fail tests for the wrong reason

For more on Salesforce sandbox types and when to use each, see our guide on how to perform Salesforce regression testing.



How to Write Good Salesforce UAT Scenarios

Focus on Business Outcomes

Weak Scenario (Too Technical)

Strong Scenario (Business Outcome)

Check the Account object stores the company name, billing address and phone number

A sales rep receives an inbound lead, creates the account, adds contacts, logs the first call and schedules a follow-up

Check the validation rule stops opportunities with negative amounts

A rep trying to give a discount above their limit is told why, and the request goes to the right person for approval

Write every scenario from the user's point of view: what they're trying to do, and how Salesforce should help.

UAT Scenario Template

ID:              UAT-SALES-07
Process:         Opportunity to quote
Role:            Sales representative (Enterprise team)
Scenario:        Create a quote for a returning customer, with a discount
                 above the rep's approval limit
Preconditions:   Account "Acme Ltd" exists with an open opportunity
                 Rep's discount limit is 10%
Steps:           1. Open the Acme Ltd opportunity
                 2. Add 3 products from the price book
                 3. Apply a 15% discount
                 4. Generate a quote and submit for approval
Expected:        The rep sees a clear message that approval is needed
                 The request goes to the rep's Sales Manager
                 The quote can't be sent until it's approved
Acceptance:      Completed in under 5 minutes, without help
Result:          Pass / Fail / Pass with comments
Tester:          [Name]          Date: [Date]
ID:              UAT-SALES-07
Process:         Opportunity to quote
Role:            Sales representative (Enterprise team)
Scenario:        Create a quote for a returning customer, with a discount
                 above the rep's approval limit
Preconditions:   Account "Acme Ltd" exists with an open opportunity
                 Rep's discount limit is 10%
Steps:           1. Open the Acme Ltd opportunity
                 2. Add 3 products from the price book
                 3. Apply a 15% discount
                 4. Generate a quote and submit for approval
Expected:        The rep sees a clear message that approval is needed
                 The request goes to the rep's Sales Manager
                 The quote can't be sent until it's approved
Acceptance:      Completed in under 5 minutes, without help
Result:          Pass / Fail / Pass with comments
Tester:          [Name]          Date: [Date]
ID:              UAT-SALES-07
Process:         Opportunity to quote
Role:            Sales representative (Enterprise team)
Scenario:        Create a quote for a returning customer, with a discount
                 above the rep's approval limit
Preconditions:   Account "Acme Ltd" exists with an open opportunity
                 Rep's discount limit is 10%
Steps:           1. Open the Acme Ltd opportunity
                 2. Add 3 products from the price book
                 3. Apply a 15% discount
                 4. Generate a quote and submit for approval
Expected:        The rep sees a clear message that approval is needed
                 The request goes to the rep's Sales Manager
                 The quote can't be sent until it's approved
Acceptance:      Completed in under 5 minutes, without help
Result:          Pass / Fail / Pass with comments
Tester:          [Name]          Date: [Date]
ID:              UAT-SALES-07
Process:         Opportunity to quote
Role:            Sales representative (Enterprise team)
Scenario:        Create a quote for a returning customer, with a discount
                 above the rep's approval limit
Preconditions:   Account "Acme Ltd" exists with an open opportunity
                 Rep's discount limit is 10%
Steps:           1. Open the Acme Ltd opportunity
                 2. Add 3 products from the price book
                 3. Apply a 15% discount
                 4. Generate a quote and submit for approval
Expected:        The rep sees a clear message that approval is needed
                 The request goes to the rep's Sales Manager
                 The quote can't be sent until it's approved
Acceptance:      Completed in under 5 minutes, without help
Result:          Pass / Fail / Pass with comments
Tester:          [Name]          Date: [Date]

For more templates and examples, see our guide to UAT test scripts.

Include Real-World Complexity

Type of Complexity

Example Scenario

Imperfect data

Duplicate accounts, missing fields or out-of-date contacts

Exceptions

The approver is on leave, or an order can only be partly fulfilled

Volume

Hundreds of records on one account, or reports covering thousands of rows

Integration failures

The ERP is unavailable when a quote is created

Permissions

A user tries to see records they shouldn't, or can't see records they need

Write Scenarios for Every Role

Role

What to Test

Sales representatives

Managing opportunities, creating quotes, logging activity and using Salesforce on mobile

Sales managers

Pipeline views, forecasts, team performance and approvals

Service agents

Resolving cases, finding knowledge articles, seeing customer history and tracking SLAs

Executives

Dashboards and reports that answer real business questions

Admins

Managing users, changing configuration and keeping data clean

Salesforce's "Log in as" feature is a quick way for admins to check what each role can see, but the real UAT should be done by people in those roles.

Test Whole Business Processes

Process

What It Covers

Lead to cash

From marketing lead to opportunity, quote, contract, order, invoice and revenue

Customer service

From case creation to assignment, resolution, communication and customer feedback

Partner management

Partner onboarding, deal registration, marketing funds and commission

Campaign to lead

From campaign planning to lead capture, scoring, routing to sales and measuring results

End-to-end scenarios often uncover integration and data sync problems that testing one part at a time misses.



Running Salesforce UAT: Manual vs Automated

The Traditional Manual Approach

In traditional UAT, business users follow written scripts step by step, record results in spreadsheets or a test tool, and work through scenarios one after another. Issues found along the way get logged, fixed and retested.

Problem

What It Means

Not enough time

Senior users can't spend weeks clicking through scripts alongside their day jobs

Technical hurdles

Users can't always tell a configuration issue from a real bug, so they wait for help

Inconsistent results

Different people follow the same script differently

Gaps in coverage

Lower-priority scenarios get squeezed out

Admin overload

Users spend more time recording results than judging whether Salesforce works

Starting from scratch every time

Each release means re-testing everything by hand

For a closer look at the trade-offs, see our guide to manual vs automated UAT testing.

Automated UAT That Business Users Still Own

Automating UAT doesn't mean taking it away from the business. It means taking away the clicking and the spreadsheets, so users can focus on judgement.

How It Works

What It Means for Business Users

Scenarios written in plain English

Users describe their own processes in their own words, so the tests reflect how they really work

Scenarios run automatically

Instead of clicking through every step, users review the results and decide whether they're acceptable

Screenshots and logs for every step

Users can see exactly what happened, without needing technical knowledge

Reusable steps

Steps like "Create opportunity" or "Submit for approval" are built once and reused, so scenarios are quick to update when processes change

Fixes proposed when screens change

When a Salesforce release or configuration change moves things around, fixes are suggested for review, so UAT scenarios stay ready

Rerun every release

Scenarios that passed last time can run again automatically, so users focus on what's new

Here's what the scenario template above might look like as an automated UAT test:

Plain English (Virtuoso QA)





A sales manager can read this test, agree it matches how quoting really works, and review the screenshots from each run before signing off.



UAT Sign-Off

Sign-off should be a real decision, backed by evidence, not a signature at the end of a deadline.

Plain text (sign-off template)

Release:              Salesforce Spring Release, Sales Cloud changes
UAT period:           [Start date] to [End date]
Processes tested:     Lead to opportunity, quoting, approvals, forecasting
Scenarios:            48 planned, 48 run, 45 passed, 3 passed with comments
Open issues:          0 critical, 1 medium (workaround documented)
Known limitations:    Mobile quote PDF layout to be improved in next release
Decision:             Accepted for go-live / Accepted with conditions / Not accepted
Business owner:       [Name, role]          Date: [Date]
Executive sponsor:    [Name, role]          Date: [Date]
Release:              Salesforce Spring Release, Sales Cloud changes
UAT period:           [Start date] to [End date]
Processes tested:     Lead to opportunity, quoting, approvals, forecasting
Scenarios:            48 planned, 48 run, 45 passed, 3 passed with comments
Open issues:          0 critical, 1 medium (workaround documented)
Known limitations:    Mobile quote PDF layout to be improved in next release
Decision:             Accepted for go-live / Accepted with conditions / Not accepted
Business owner:       [Name, role]          Date: [Date]
Executive sponsor:    [Name, role]          Date: [Date]
Release:              Salesforce Spring Release, Sales Cloud changes
UAT period:           [Start date] to [End date]
Processes tested:     Lead to opportunity, quoting, approvals, forecasting
Scenarios:            48 planned, 48 run, 45 passed, 3 passed with comments
Open issues:          0 critical, 1 medium (workaround documented)
Known limitations:    Mobile quote PDF layout to be improved in next release
Decision:             Accepted for go-live / Accepted with conditions / Not accepted
Business owner:       [Name, role]          Date: [Date]
Executive sponsor:    [Name, role]          Date: [Date]
Release:              Salesforce Spring Release, Sales Cloud changes
UAT period:           [Start date] to [End date]
Processes tested:     Lead to opportunity, quoting, approvals, forecasting
Scenarios:            48 planned, 48 run, 45 passed, 3 passed with comments
Open issues:          0 critical, 1 medium (workaround documented)
Known limitations:    Mobile quote PDF layout to be improved in next release
Decision:             Accepted for go-live / Accepted with conditions / Not accepted
Business owner:       [Name, role]          Date: [Date]
Executive sponsor:    [Name, role]          Date: [Date]



Salesforce UAT Checklist

  • Scope agreed, covering processes, roles and integrations

  • Business owners, power users and experts named and available

  • Acceptance criteria written and measurable

  • UAT sandbox set up, with changes frozen

  • Realistic, masked or synthetic data loaded

  • Users given the same permissions they'll have in production

  • Connected systems available for end-to-end scenarios

  • Scenarios cover normal paths, exceptions and every key role

  • Issue logging and fixing process agreed

  • Results recorded with evidence

  • Sign-off decision made by business owners



Building a Salesforce UAT Programme

Stage

What to Do

Pilot

Pick one important process, like opportunity management or case resolution. Involve real business users, not proxies. Measure UAT time, users' time, issues found and how confident people feel

Expand

Add more processes, starting with revenue, regulated and adoption-critical ones. Build a library of reusable steps by business area

Embed

Make UAT a standard part of every Salesforce release, not a one-off project. Train business users to write their own scenarios

Keep it current

Review scenarios every quarter, and retire outdated ones. When a bug reaches production, ask why UAT missed it, and add a scenario



How Virtuoso QA Helps with Salesforce UAT

What You Need

How Virtuoso QA Helps

Scenarios business users can write and read

UAT scenarios are written in plain English, so they read like process documentation. Business users can write, review and agree them without technical help

Scenarios from your requirements

Touchstone reads your user stories and specs and drafts requirements and scenarios, each citing its source, with a named person approving each one

Less clicking, more judgement

Scenarios run automatically, and capture screenshots and logs at every step, so users review outcomes rather than click through them

Scenarios that survive Salesforce changes

Virtuoso QA finds elements by label, position and context, and handles Lightning's dynamic pages. When a release or configuration change breaks a step, it suggests a fix for your team to accept or reject

Reusable business steps

Build steps like "Create opportunity" or "Generate quote" once, and use them across every scenario

Whole processes

One scenario can go through Salesforce, call APIs and check connected systems

Evidence for sign-off

Every run records what was tested, against which requirement, the result and who approved the test

When it's time to sign off, Virtuoso QA's release evidence gives business owners every scenario, result and approval in one place.

To see it working on your own org, take a look at Virtuoso QA's Salesforce test automation.

To explore how Virtuoso QA automates Salesforce end-to-end, watch the detailed walkthrough in the video below:



Related Reads

Salesforce UAT FAQs

How long should Salesforce UAT take?

What test data should I use for Salesforce UAT?

Should UAT scenarios include negative testing?

How often should we perform Salesforce UAT?

Can business users create UAT test cases without technical help?

Written by

Rishabh Kumar

AI Testing & Quality Engineering Contributor

Rishabh leads business development and marketing at Virtuoso QA. He writes about AI-powered test automation, end-to-end testing, self-healing tests, and quality engineering, exploring how these capabilities can improve test coverage, reduce test maintenance, and support reliable software releases.

See what your next release looks like with Virtuoso

Book a walkthrough on your applications and your workflows. Bring a requirement, a user journey, or a brittle Selenium script, and watch the loop run on something you recognise.

See what your next release looks like with Virtuoso

Book a walkthrough on your applications and your workflows. Bring a requirement, a user journey, or a brittle Selenium script, and watch the loop run on something you recognise.

See what your next release looks like with Virtuoso

Book a walkthrough on your applications and your workflows. Bring a requirement, a user journey, or a brittle Selenium script, and watch the loop run on something you recognise.

Virtuoso QA is establishing the standard of proof for software releases. Its governed QA loop turns business requirements into tests for any browser-based application: AI proposes, a deterministic engine executes, a person approves what matters, and every decision leaves evidence.

Trust Center

AICPA

SOC

WAVE STRONG PERFORMER

@ Copyright 2026 SpotQA, Creators of Virtuoso QA

Virtuoso QA is establishing the standard of proof for software releases. Its governed QA loop turns business requirements into tests for any browser-based application: AI proposes, a deterministic engine executes, a person approves what matters, and every decision leaves evidence.

Trust Center

AICPA

SOC

WAVE STRONG PERFORMER

@ Copyright 2026 SpotQA, Creators of Virtuoso QA

Virtuoso QA is establishing the standard of proof for software releases. Its governed QA loop turns business requirements into tests for any browser-based application: AI proposes, a deterministic engine executes, a person approves what matters, and every decision leaves evidence.

Trust Center

AICPA

SOC

WAVE STRONG PERFORMER

@ Copyright 2026 SpotQA, Creators of Virtuoso QA