Free tools / Salesforce UAT test plan generator
Pick the Salesforce clouds and processes in this release. You get plain-English test cases for each role, entry and exit criteria, a defect process and a sign-off sheet, ready to download for Word and Excel. Free, and nothing you enter leaves your browser.
01 // your release
02 // what's in scope
Pick the clouds this release touches, then untick processes that didn't change.
Sales Cloud
Service Cloud
03 // who tests
Roles come from your processes. Add any others, like a regional manager or partner user.
04 // extras
// your uat plan //
test cases for Salesforce release
The plan covers scope, roles, environment, entry and exit criteria, defect severities, a defect log and a sign-off sheet.
Testing 14 cases by hand every release? See what it costs →Preview: 14 test cases
Nothing you enter leaves your browser.
Given a new prospect submits the web-to-lead form. When the lead is created in Salesforce. Then assignment rules route it to the correct owner or queue, and the owner is notified.Sales RepHigh
Given a qualified lead I own. When I convert it. Then an account, contact and opportunity are created with the mapped fields, and no duplicate account is created.Sales RepHigh
Given an account that already exists with the same name and website. When I create or convert a matching lead. Then the duplicate rule warns or blocks me, as the business agreed.Sales RepMedium
Given an open opportunity. When I move it through each stage. Then required fields are enforced at each stage and the probability updates.Sales RepHigh
Given an opportunity with a discount above the approval threshold. When the rep submits it for approval. Then it reaches me, I can approve or reject it, and the rep is told the decision.Sales ManagerHigh
Given opportunities owned by my team and by other teams. When I open the pipeline dashboard. Then I see only my team's records, and the totals match the underlying report.Sales ManagerMedium
Given a customer emails the support address. When the email arrives. Then a case is created, linked to the right contact, and the customer gets an auto-response.Service AgentHigh
Given a new case of each type and priority. When it is saved. Then it routes to the correct queue or agent.Service AgentHigh
// how uat works //
UAT is the last check before a change reaches production. Business users run real tasks in a sandbox, under their own logins, and decide if the release is ready. Every failed case loops back through a fix and a retest before sign-off.
// where uat happens //
Each change moves through sandboxes before it reaches production. UAT belongs in a Full sandbox, or a Partial Copy seeded with the data your cases need, so business users test against something that looks like production.
Refresh the UAT sandbox before each cycle. Stale configuration and old data hide the bugs your users will find in production.
// anatomy of a test case //
1
SVC-01 · High
2
Tester: Service Agent
3
Scenario: Customer email becomes a case
4
Given a customer emails the support address
When the email arrives
Then a case is created for the right contact, and the customer gets an auto-response
5
Result: Pass · Evidence: screenshot · Defect: none
1
ID and priority
Lets testers sort and track the run. Run every High case first.
2
Tester role
Test as the real role, never as an admin. Admins see everything, so sharing bugs slip through.
3
One scenario
One business outcome per case, named the way your users talk about it.
4
Given, When, Then
Plain-English steps a business user can follow and an automation tool can run.
5
Result and evidence
Pass or fail, a screenshot and a defect ID, so sign-off has proof behind it.
// what’s in the plan //
Nine parts. The generator fills in the test cases, roles and criteria for you; you add names, dates and the sandbox.
01 //
Scope
The clouds, processes and integrations in this release, and what is out of scope.
02 //
Roles and testers
One named tester per role, logging in with that role’s real profile.
03 //
Environment
Which sandbox, when it was last refreshed, and how testers log in.
04 //
Test data
The records each case needs, created fresh before testing starts.
05 //
Entry criteria
What must be true before UAT starts, like QA done and no open critical bugs.
06 //
Test cases
Plain-English scenarios with an expected result, a priority and a tester.
07 //
Defect process
How to log a bug, what each severity means, and who fixes and retests.
08 //
Exit criteria
The pass rate and open-bug limits that make the release ready.
09 //
Sign-off
Who approves go-live, recorded with name, role, decision and date.
// from our calls //
01
Testing as an admin
Admins see every record, so sharing and permission bugs slip through. Give each tester a user with the real profile and permission sets.
02
Stale sandbox data
One team told us they refresh their full sandbox only twice a year. Old data hides the bugs users hit in production. Refresh before each UAT cycle, or seed fresh data.
03
Rebuilding test data by hand
Teams spend hours recreating the same records in every environment before they can test. Script your test data so every run starts clean.
04
Skipping the end-to-end flow
Bugs like currency rounding between Salesforce and an ERP only show up when you test the whole flow. Include at least one full quote-to-cash or case-to-resolution run.
// keep going //
Plan the rest of your release
// release calendar //
When does Spring ’27 reach your org?
Look up your instance’s preview and upgrade dates, then book your UAT window before them.
Check my dates →
// calculator //
What does each release cost your team in regression?
UAT checks this change. Regression checks everything else, three times a year. Put a number on it.
Open the calculator →
// free tools //
More free tools for Salesforce QA teams
Calculators, playbooks and open-source tools in one place. No sign-up needed for the calculators.
Browse free tools →
// questions //
Questions about Salesforce UAT
What is UAT in Salesforce?
User acceptance testing is the last check before a change goes live. Business users run their everyday tasks in a sandbox, under their own roles, and confirm the change works the way they need. It ends with a sign-off: go or no-go.
Who should do UAT in Salesforce?
Which sandbox should I use for UAT?
How long should Salesforce UAT take?
What is the difference between UAT and regression testing?
Can Salesforce UAT be automated?
// next step //
Run your UAT cases automatically
Paste the generated scenarios into TestZeus and run them as each role in your sandbox. Business users read the results in plain English and spend their time on sign-off, not on clicking.
// Start testing //
