10,853
edits
Salesforce admins: Urgent action required!
Preview: Difference between revisions
Jump to navigation
Jump to search
→How to test
| Line 6: | Line 6: | ||
Beta testing will help you identify a problem before it becomes one. | Beta testing will help you identify a problem before it becomes one. | ||
Before each official release (Spring, Summer, Autumn & Winter Update), we strongly recommend testing the beta and | Before each official release (Spring, Summer, Autumn & Winter Update), we strongly recommend testing the beta and verifying that the new version works well within your environment. | ||
We want to help you avoid any issues a new update might cause to you. This is particularly beneficial for those who have a very heavy customization in place or peculiar settings on the server side. | We want to help you avoid any issues a new update might cause to you. This is particularly beneficial for those who have a very heavy customization in place or peculiar settings on the server side. | ||
A beta version also provides preview access to the upcoming new features, so you can explore and try the new functionalities, see if and how they interact with your existing solutions | A beta version also provides preview access to the upcoming new features, so you can explore and try the new functionalities, see if and how they interact with your existing solutions and provide feedback if you wish to do so. | ||
Note: We recommend using beta versions against an environment where it is safe if everything doesn't work 100% correctly such as Dev, Testing, or Pre-Prod. It is a beta version, so it is not guaranteed that errors or problems might not occur – and it is one of the main points of a beta version to try identifying them. On the other hand, the more similar the environment to the actual production the better, since data volume, configuration details, and other specifics might matter. For more info, see [https://blog.resco.net/2019/11/28/beta-testing-reduce-risks/ How can Beta Testing reduce risks before the official App Update] {{Badge|Blog}}. | Note: We recommend using beta versions against an environment where it is safe if everything doesn't work 100% correctly such as Dev, Testing, or Pre-Prod. It is a beta version, so it is not guaranteed that errors or problems might not occur – and it is one of the main points of a beta version to try identifying them. On the other hand, the more similar the environment to the actual production the better, since data volume, configuration details, and other specifics might matter. For more info, see [https://blog.resco.net/2019/11/28/beta-testing-reduce-risks/ How can Beta Testing reduce risks before the official App Update] {{Badge|Blog}}. | ||
== How to test == | |||
The easiest way to get started: | |||
# Install the beta app on your device. | |||
# Synchronize with your test/dev organization. | |||
# Walk through the most common tasks or the most heavily customized parts of your project. | |||
If you have a willing and competent field technician, you can give him or her a second device with the beta app. The technician should then perform the daily routine on two devices (production app with production organization and beta app with test/dev server). If everything works correctly - you're ready for the upgrade. | |||
If you're ready to spend more resources, consider installing beta Woodford on your test/dev environment. This will allow you to get acquainted with the new features we have prepared, and even provide feedback to shape the new features to better match your needs. | |||
== Where to find beta releases == | == Where to find beta releases == | ||