Salesforce release and critical update regression testing
When a Salesforce release becomes available, performs regression testing on the supported versions of the product to ensure core features function as expected. Supported versions include the latest version and the previously released version of the product. For more information on 's product support policy, visit Release process. For critical update regression testing results from the latest Salesforce release, visit Winter '25 test results.
Special considerations
Regression testing considerations include:
-
only performs regression testing on supported versions of . Unsupported versions of the product are not regression-tested against Salesforce releases. For more information on 's product support policy, visit Release process.
-
If your Salesforce environments utilize custom code, customizations, or configurations, highly recommends you test the Salesforce release in your environments to determine the impact. only tests Salesforce updates in an out-of-the-box environment.
-
Ensure your browsers are up-to-date. Issues are often found and easily fixed by ensuring your browser is current. Therefore, it is recommended that you check for updates, install any that are available, and restart your browser.
Regression testing timeline
The regression testing timeline for a Salesforce release is as follows:
-
Salesforce publishes release notes.
-
reviews the release notes and identifies areas of concern to test.
-
Salesforce sandbox previews become available.
-
performs regression testing. Visit Regression Testing Protocol.
If an issue is found, creates a Salesforce case to find out if the issue will be fixed before production release or not.
-
publishes regression testing results.
Note: Results are published as soon as testing is complete. If no test results are posted, testing is still in progress.
Regression testing protocol
performs all regression testing in an out-of-the-box environment that has all Salesforce critical updates that are available in the test environment enabled. The product is considered out-of-the-box when no custom code, customizations, or configurations, such as custom integrations, custom formulas, or custom workflow, have been added to the product.
Note: In addition to performing regression testing in the latest version of Salesforce, the engineering team utilizes the most recent versions of the Salesforce platform in product development. This includes the sandbox preview for soon-to-be-released versions of Salesforce.
regression testing includes:
- Installing the latest released version of the product in the newly released version of Salesforce.
Note: does not test the installation of older versions of the product.
-
Upgrading the product from two releases ago to the previous release and from the previous release to the current release.
-
Completing a post-installation verification test to ensure the product is largely working. The post-installation verification test outlines the most commonly performed user actions in the product, such as creating and editing instances of all major objects, searching for and attaching documents, and creating and editing an HCP.
-
Investigating and thoroughly testing all critical updates and any additional updates that could have a significant impact on the product. As soon as the Salesforce release notes are available, develops risk-based test protocols beyond the actions included in the post-installation verification test.
If identifies an issue during regression testing, creates a known issue for it. The known issue includes a recommendation on how to bypass the issue. In addition, if the issue is considered critical, releases a hotfix or maintenance release of the product that resolves the issue and provides email communication to customers regarding the hotfix. If the issue is not considered critical, provides a fix for the issue in the next major release of . For more information on known issues and hotfix releases, visit Known issues and Release Process.