Salesforce Sandbox Preview Testing
Salesforce sandbox preview testing is how teams evaluate an upcoming seasonal release before it reaches production. Salesforce upgrades a subset of sandboxes to the next version during a defined preview window, giving you a safe environment to run impact analysis and focused regression against your own configuration ahead of general availability.
The mechanics of the preview window, and how to use it well, for every Spring, Summer, and Winter release.
How the sandbox preview window works
Ahead of each seasonal release, Salesforce upgrades preview instances to the upcoming version before upgrading production. Sandboxes that sit on a preview instance receive the new release early, which is what creates the preview window: a period in which your team can work in the next version while live users remain on the current one.
Not every sandbox previews. Whether a sandbox is on the upcoming release depends on the instance it runs on, so the first practical step is knowing which of your sandboxes are preview and which are not.
The distinction matters more than it first appears. Running release testing against a non-preview sandbox produces results for the current version, not the one that is about to arrive, which can create false confidence. Equally, a preview sandbox that has drifted far from production configuration will surface issues that do not exist in the live org, or miss ones that do. The value of the preview window depends on testing the right version in an environment that genuinely resembles production, so confirming both facts before testing begins is time well spent.
| Aspect | Preview instance sandbox | Non-preview instance sandbox |
|---|---|---|
| Version during preview | Upgraded to the upcoming seasonal release early. | Remains on the current production release. |
| Use for release testing | Suitable for testing the next release before general availability. | Not suitable for previewing changes; matches live behavior instead. |
| Best used for | Impact analysis and focused regression on the upcoming version. | Current-version work, training, and support reproduction. |
Sandbox preview testing is one activity within the broader release program. For the end-to-end method, see the Release Intelligence pillar, and for turning release notes into a scored list of what to test, see release impact analysis.
Using the preview window well
The preview period is finite, so the sequence you follow inside it determines how much genuine validation gets done. The most common way teams lose the window is by spending its first days deciding what to test; a defined lifecycle removes that hesitation and keeps the work focused from day one.
Identify a representative preview sandbox
Confirm you have a preview-instance sandbox that reflects production configuration. If it is stale, plan a refresh so the environment mirrors the org you actually run.
Run impact analysis on day one
Map the upcoming release against your metadata immediately, so the rest of the window is spent testing rather than reading release notes and guessing at scope.
Execute focused regression
Run the tests tied to the affected components and processes. Execution can be handled through test automation so the compressed window is used efficiently.
Validate mandatory changes early
Test any Release Update due to enforce so nothing becomes mandatory in production without having been checked in the preview version first.
Record readiness before general availability
Capture results and outstanding risk while still in preview, so the production window is entered with evidence rather than open questions.
How SyntraFlow is designed to support preview testing
These capabilities help teams get the most out of a finite preview window. As SyntraFlow expands its Salesforce coverage, they are available for demonstration and proof-of-concept validation.
Preview sandbox connection
Designed to connect to a preview-instance sandbox on the upcoming version and build a component inventory, drawing on metadata intelligence.
Early impact mapping
Designed to map the upcoming release to your components at the start of the window, so the analysis is ready before testing begins.
Focused test selection
Designed to assemble a regression set scoped to what the release affects, so the finite window is not spent re-running the entire suite.
Preview execution
Designed to run selected tests against the preview sandbox, with execution handled through test automation as the run mechanism.
Readiness tracking
Designed to show which previewed areas are validated, in progress, or blocked, tracked against the general-availability date.
Preview evidence
Designed to compile analysis and results from the preview period into evidence that supports a documented sign-off before go-live.
Preview the cross-system flow, not just the org
A preview sandbox shows how the upcoming release behaves inside Salesforce, but many risks only appear where Salesforce connects to other systems. SyntraFlow's origin in enterprise ERP testing means it is designed to use the preview window to validate the end-to-end flow, following a process from the preview sandbox through the integration layer into the connected system.
Anchored by the Oracle ERP testing tool, this lets a team confirm during preview that a coming release will not break a downstream order or invoice once it reaches production.
What good preview testing delivers
Using the preview window deliberately changes the release from a risk to a planned checkpoint.
Issues found before users are affected
Testing in preview surfaces problems while live users remain on the current version and there is still time to react.
A window used efficiently
Front-loading impact analysis leaves the bulk of the finite window for testing rather than investigation.
Confidence in the environment
Knowing which sandboxes preview, and keeping them representative, means results reflect how production will actually behave.
Readiness before go-live
Recording results during preview means the production window is entered with documented evidence, not open questions.
Sandbox preview testing FAQs
What is a Salesforce preview sandbox?
A preview sandbox is a sandbox on a preview instance that Salesforce upgrades to the upcoming seasonal release before production. It lets teams evaluate the new version against their own configuration, run impact analysis, and complete focused regression ahead of general availability.
Do all sandboxes get the preview release?
No. Whether a sandbox previews depends on the instance it runs on. Preview-instance sandboxes are upgraded to the upcoming release early, while non-preview sandboxes stay on the current production version. Confirm which of yours are preview before planning release testing.
When does the preview window open?
Salesforce publishes preview and production dates for each seasonal release in advance. Preview sandboxes are upgraded ahead of production, which opens a defined window for testing the next version. Plan to start impact analysis as soon as that window opens.
Should I refresh my sandbox before preview testing?
If the sandbox no longer reflects production configuration, a refresh helps ensure results are meaningful. The goal is a preview-instance sandbox that mirrors the org you run, so what you observe in preview matches how production will behave after the release.
What should I test during the preview window?
Focus on the components and processes the upcoming release affects, plus any Release Update due to enforce. Impact analysis narrows the release to what intersects your org so the finite window is spent on genuine risk rather than the whole suite.
How does SyntraFlow use the preview window?
SyntraFlow is designed to connect to a preview sandbox, map the release to your components early, select a focused regression set, and track readiness to sign-off. As its Salesforce coverage expands, these capabilities are available for demonstration and proof-of-concept validation.
Make the most of every preview window
See how SyntraFlow is designed to turn the sandbox preview period into focused, evidence-based release validation before general availability.