Review what you need to do to set your sandbox up for a release preview
Review the Release Preview for new features
Skim through the Release Notes for additional features
Prepare a list of features you wish to test
Understand all “auto enabled” features
After your sandbox has been upgraded:
Develop a document you use each release to test, don’t reinvent the wheel each time
Review all features you have listed to test
Test key business processes in your Sandbox. You should not have any issues but it is a best practice to run
through your key business processes.
Review all “auto enabled features” and determine end user impact
Develop any training materials needed for your users
Check for any IP addresses to white list
a. Focus on the areas in your org which are highly customized
b. Start with the areas where you have programmatically customized things using Apex & Visualforce
c. A good start is to “Run All Tests”, this may be obvious, but I bet it gets forgotten.
d. Apex and Visualforce is actually pretty robust as Salesforce maintain backward compatibility through the
API versioning - But these areas by their very nature are complex, Salesforce doesn’t know what you done. Have you followed best practices or not. Have you bent the system like no other! Nothing is bullet proof!
e. Next you should test the business processes where you have used any of the declarative tools.
f. So any Flows, Processes, Workflow Rules, Approvals Rules -- these areas tend can get complex linking
many different processes and records within your org! Test them!
Test your apps from the appexchange
a. You will want to highlight processes in your test list which are dependent on apps installed in your org
b. Apps used once in awhile should have low priority. Remember testing takes time
c. It’s worth paying attention to any apps which are unmanaged which your users are heavily reliant on -
these tend to be less tested because they are normally free or open source