Salesforce
How to Test Salesforce Release Updates Before Enforcement

Rishabh Kumar
Published On

Table of contents
Lorem ipsum
Lorem ipsum
Lorem ipsum
Lorem ipsum
Lorem ipsum
How Do You Test Salesforce Release Updates?
A Salesforce release update is a change to platform behaviour that Salesforce makes available for a period before enforcing it in every org on a published date.
To test one, find it on the Release Updates page in Setup, switch on its test run in a sandbox if it offers one, run the journeys it could affect end to end, fix what breaks, then enable it in production on your own schedule, before Salesforce does it for you.
Release updates deserve more attention than the headline features of a release. New features usually arrive switched off. Release updates arrive switched on, eventually, whether you're ready or not. And once enforced, they don't roll back.
How Release Updates Work
Release updates replaced what Salesforce used to call critical updates. They all live on one page in Setup.
Search Release Updates in the Quick Find box, and each update shows what it changes, the steps Salesforce recommends and the date by which those steps must be done.
Every update moves through the same three stages.
Introduced: The update appears on the Release Updates page, usually with a release or two of notice.
Optional: You can read the guidance and, for many updates, enable a test run. A test run switches the new behaviour on temporarily, so you can see what it does to your org, and switch it off again if something breaks.
Enforced: On the enforcement date, usually tied to a major release, Salesforce turns the update on in every org.
Three details catch teams out.
Not every update supports a test run, and for those, Salesforce describes how to test in the release notes instead. Enforcement dates move, because Salesforce postpones some updates and occasionally withdraws one, so last quarter's spreadsheet may already be wrong. And enforcement is one way. Once an update is enforced, you fix forward, which is why the testing has to happen while the switch is still yours.
Want to know when the sandbox preview opens, and how long your testing window really is? It's all in Salesforce release cycle.
Step by Step, from Inventory to Production
Inventory Every Pending Update
Open Release Updates in production and in your main sandbox, and give each update an owner.
Map Each Update to Journeys
Ask which business journeys could feel it. An authentication update touches every integration that logs in. A redirect update touches flows that send users somewhere afterwards. A permissions update touches anyone who isn't an administrator.
Find the Hidden Dependencies
Search your metadata, integration settings and middleware for whatever the update changes, such as an old login method, a hard-coded URL or a field another component reads. The dependency nobody remembers is the one that breaks.
Enable the Test Run in a Sandbox
Use a production-like sandbox, with integrations pointed at test endpoints. If there's no test run, follow Salesforce's testing instructions instead.
Run the Affected Journeys End to End, as Real Users
Not only as an administrator, and not only inside Salesforce. If an update changes how integrations authenticate, the real test is whether the order still reaches the ERP.
Fix, Then Retest
Change the configuration, code or integration, then run the same journeys again with the test run still on.
Enable in Production on Your Own Terms
Once the sandbox is clean, deploy the fixes and enable the update in a quiet window, ahead of enforcement. A surprise should land when your team is watching, not on an upgrade weekend.
Keep the Evidence
Record which journeys were tested against which update, the results, the fixes and who approved enabling it.
Authentication updates break every test at once, so they deserve a plan of their own. Keep test logins working through them with handling Salesforce login, MFA and SSO in automated tests.
A Release Update Register You Can Copy
Most teams track release updates in a spreadsheet nobody owns. A register with these columns turns it into a plan.
Column | What to record |
|---|---|
Update | Name, as shown on the Release Updates page |
Category | Authentication, URLs, access, Apex and API, interface, or calculations |
Enforcement date | As currently published, checked each release |
Test run available? | Yes or no. If no, link the release note’s testing instructions. |
Journeys at risk | The business journeys and integrations it could affect |
Personas to test as | The roles whose access or experience could change |
Owner | One named person |
Status | Not started, testing, fixes in progress, enabled in production |
Evidence | A link to the run results and the approval |
The evidence column is far easier to keep when every test already links to the requirement it proves, the idea behind a requirements traceability matrix.
Which Release Updates Break Which Journeys
The category tells you where to look before you’ve read a word of the guidance.
Category | What tends to break | Where to test |
|---|---|---|
Authentication and integration security | Integrations using older login methods, connected apps, scheduled jobs | Every inbound and outbound integration, end to end, including the downstream system |
URLs and redirects | Hard-coded instance URLs, redirects after flows or Visualforce pages, embedded content | Integrations, bookmarks and guided flows that return users to a page |
Access and visibility | Logic that reads data the running user can no longer see, approvals that branch on it | The same journey as each persona, especially non-admin users |
Apex and API behaviour | Code relying on older defaults for sharing, user mode or API version | Automation running as different users, integrations pinned to older API versions |
User interface and accessibility | Custom components and heavily customised pages | Critical record pages, including at high browser zoom |
Calculations | Values computed differently after a fix | Any journey that produces an amount, a tax or a date |
A Recent Example, Winter '27
The Winter ‘27 release, which reached production between September and October 2026, enforced a typical mix. The most disruptive was the retirement of the OAuth username-password flow, so any integration still logging in with a username, password and security token stopped working on upgrade weekend. Alongside it came profile name filtering, which stops users seeing other users’ profile names without the right permission and quietly empties logic that depended on them. There was also enforcement of My Domain URLs in place of hard-coded instance URLs, and accessibility changes to page components at 200% browser zoom.
Notice how few of those would show up in a test that logs in as an administrator and clicks through Salesforce alone.
The first breaks an integration overnight. The second sends an approval down the wrong branch, with no error. The third breaks something a departed admin set up years ago. The last only appears for users who work zoomed in.
Zoom changes are one reason accessibility belongs in every release cycle. Read more in Salesforce accessibility testing.
Testing Release Updates with Virtuoso QA
Your team decides which journeys an update could affect. Virtuoso QA runs them against the sandbox with the test run switched on, as each persona rather than as an administrator, on its deterministic engine.
When something fails, Touchstone classifies the failure as an application defect, test brittleness, an environment problem, data or configuration drift. A behaviour change caused by the update isn't mistaken for a moved button. Every proposal, approval and change is versioned and recorded with who made it, alongside the run results, which gives you the register's evidence column for free.
Virtuoso QA's Salesforce test automation runs the journeys each update could affect, as every persona, with the test run switched on, so you enable updates on your schedule, not Salesforce's.
Frequently Asked Questions
What is a Salesforce Release Update?
Where Do I Find Release Updates?
What Does Enable Test Run Do?
Can I Postpone a Release Update?
Can I Roll Back a Release Update After Enforcement?
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.










