UAT Studioby Salvion
Salesforce UAT

User acceptance testing for Salesforce

For the go-live of Sales Cloud or Service Cloud, and for the three Salesforce releases that follow every year. Business testers get their own scripts, issues come in with the screenshot and the record, and the steering committee gets a clear go/no-go.

Testers never need a licenceReady-made scripts for Sales Cloud and Service CloudData stored in the EU
Start a free 14-day pilotSee pricing
Who it is for

For everyone in a Salesforce UAT

UAT Studio was built from real Salesforce go-lives, by a consultant who ran them himself.

Test leads and project managersPlan the test days, follow progress per group and run the triage.
Salesforce admins and developersSend issues to Jira or Azure DevOps and see at once what to retest.
Implementation partnersRun the UATs of all your clients in one place, with your own logo on the Partner plan.
Business testersSales reps and service agents who test their own processes, without training in a test tool.
Process owners and the steering committeeSign off per group and decide on the go/no-go with facts.
The hard parts

What makes a Salesforce UAT hard, and how UAT Studio handles it

A CRM UAT is tested by people who do not test for a living, in an environment that keeps changing, against a date that does not move. This is how UAT Studio handles each part.

Business testersPeople who test once or twice a yearYour testers are sales reps and service agents with a day job. They need a clear script and one place to record what they see.
  • They sign in with a code by email: no account, no password, no licence
  • Each tester sees only their own scripts, and records Pass, Fail, Blocked or N/A per step
  • On a laptop, a tablet or a phone
  • The browser extension for Chrome and Edge opens their tests in a side panel next to Salesforce; your test lead tells testers where to get it
SandboxesWhich sandbox, which build?The UAT runs in a sandbox, and fixes arrive while testing goes on. Everyone has to know what was tested where.
  • The environment, release and build are kept per round, and shown on the go/no-go report
  • An issue links straight to the Salesforce record where it went wrong, sandbox included
  • A fail in the side panel takes a screenshot, the record link and the error messages of the page along
Test dataThe right user and the right recordsA quote approval can only be tested by the right profile, with the right account and price book. Testers lose hours when that is not ready.
  • A test role and a test account per tester: their script says Log in as …
  • Test data per step, next to the action and the expected result
  • Notes for testers for test mailboxes, naming rules and who to call
  • Export or delete everything at the end of a project
The release calendarThree releases a yearSpring, Summer and Winter: each Salesforce release can change how your org works, and reaches your sandboxes weeks before production.
  • The projects page shows the coming Salesforce releases, with the date of the sandbox preview, the date of production and the release notes
  • Admins get an email two weeks before the sandbox preview
  • Start a regression round copies the test cases of an earlier UAT, with their steps, test data and expected results: Must only, Must and Should, or all
Sign-offA decision the business stands behindThe go-live is decided by the business, not by the project. They need to see what was tested and what is still open.
  • Sign-off per group: Accepted, Accepted with conditions or Rejected
  • By default, no acceptance while a Critical issue is open
  • The go/no-go report as a PDF or slides, and an evidence pack for auditors

New to a Salesforce UAT? The sandbox, test data, testers and sign-off, step by step: Read the guide.

Release readiness

Know which test cases a Salesforce release touches

Salvion keeps the changes of each Salesforce release, filed under a part of Salesforce and checked. Add the packages from AppExchange you use, or paste their release notes yourself.

What this project usesTick once on Setup which parts of Salesforce your UAT covers. Only the changes under those parts count.
Review the releaseAI shows your test cases the release touches, with the reason, proposes test cases for what is not covered yet and lists the required updates for your admin, with their dates.
The regression roundCreate it with exactly the test cases you chose. A reminder comes when it is not signed off 3 days before production, and the release report goes into the go/no-go report.

An add-on of €99 per month for every plan: add it under Plan & billing. What goes to the AI

Start faster

Start from what you already have

Template library SalesforceReady-made UAT scripts for Sales Cloud and Service Cloud: web-to-lead, lead conversion, opportunities and price books, quotes and approvals, email-to-case, routing, entitlements, the Service Console, knowledge and access per role. An add-on to every paid plan; the test cases you import stay yours.
An example projectAdd a Salesforce example to your workspace: a complete project with test cases, testers, results and issues to click through, with fictional data.
Your own test casesImport them from Excel, or from exports of Jira (Xray, Zephyr Scale), Azure DevOps and TestRail.
AI test designTest cases proposed from your user stories in Jira or Azure DevOps. You approve each one. How it works
Automated tests next to the UATThe JUnit report of Provar, Copado or your own tests on the dashboard, next to the results of the business. An add-on of Team, included in Business and up. Automated tests
Questions

Salesforce UAT: questions we hear often

Does UAT Studio need access to our Salesforce org?

No. Testers work in your sandbox as they always do. UAT Studio does not read data from your org: the browser extension only sends what a tester saves with a failed step, such as the screenshot and the link to the record.

Do our testers need a licence?

Not for UAT Studio. Testers are unlimited in every paid plan. You add their email address and they sign in with a code. In Salesforce they use the test accounts of your sandbox.

Can we use the same test cases for the next Salesforce release?

Yes. Choose Salesforce as the CRM of the project. Before each release, Start a regression round copies the test cases you choose into a new project, named after the release, such as Salesforce Spring '27.

Where do the test cases come from?

Import them from Excel or from an export of Jira, Azure DevOps or TestRail, start from the template library, or let AI propose them from your user stories. You approve each proposal.

Which test cases does the next release touch?

With the Release readiness add-on, Review the release shows the test cases each Salesforce release touches, with the reason, proposals for new test cases and the required updates with their dates. Then you create the regression round with exactly those test cases.

Where is our data stored?

In the EU (Frankfurt). See For procurement and IT for security, the sub-processors and the data processing agreement.

Try it on your next Salesforce release14 days free, with your own test cases and the connections included.Start pilot

See also Dynamics 365 UAT, the UAT checklist and all integrations. Salesforce, Sales Cloud and Service Cloud are trademarks of Salesforce, Inc. UAT Studio is not affiliated with or endorsed by Salesforce.