Use the same account next time to pick up where you left off.
|Production Salesforce account||Developer Edition or Admin Playground|
|Do I need to be a Salesforce customer?||Yes||No (It's free!)|
|Can I use it to create my Trailhead profile and store my badges?||Yes||Yes|
|Can I use it to complete Trailhead challenges?||No (except for multiple choices quizzes)||Yes|
|Can I keep my Trailhead badges if I leave my company?||No||Yes (use a personal email address)|
Sandboxes create copies of your Salesforce org in separate environments. Use them for development, testing, and training, without compromising the data and applications in your production org. Sandboxes are isolated from your production org, so operations that you perform in your sandboxes don’t affect your production org, and conversely.
Refresh your sandbox periodically to update it with data and metadata components from production. Refreshing sandboxes ensures that your sandbox doesn’t miss any changes that were deployed to production by another sandbox or manually introduced in production. When you refresh a sandbox, Salesforce rebuilds your environment and erases its old contents. The content in your new sandbox is replaced with a copy of the production org. Beware that it’s possible to overwrite all the development you’ve done in your sandbox. Therefore, it’s a good practice for each developer to have their own sandbox and make their own backups. Establish a process with the rest of the team for refreshing sandboxes.
|Developer||Developer Pro||Partial Copy||Full|
|Refresh Interval||1 day||1 day||5 days||29 days|
|Size||200 MB||1 GB||5 GB||Same as production|
|Templates and Sampling||No & No||No & No||Yes & Yes||Yes & No|
|Bundled Developer Sandboxes||N/A||5||10||15|
Full sandboxes are required only for performance and scalability testing, as well as for staging before final deployment. You might also need a Full sandbox to test triggers that make non-selective queries. For all other use cases, a partial copy of data is enough. For testing, it’s often better not to copy data at all, but rather load the same set of data every time. Data is time consuming to copy, and a large volume of data can take days to complete.
|Use Case||Developer||Developer Pro||Partial Copy||Full|
|Batch Data Test|
|Performance and Load Testing|
If you have a Partial Copy or Full sandbox, you can pick which standard and custom objects to copy over from production by using sandbox templates. Sandbox templates help you limit the size of your sandbox by limiting the data that is copied over. Generally, you need only a representative set of data for testing in sandbox, not all the data from production. Reducing the amount of data that is copied to sandbox can significantly reduce the sandbox copy time.
The sandbox template editor understands the object relationships defined in your org’s schema. Some objects are always included because they’re required in any org. As you select objects to copy, the editor ensures that the associated required objects are added.
You might think it’s more convenient to use a Partial Copy or Full sandbox, and simply avoid having to load data, but that’s not necessarily better than loading test data. Data on the production org changes all the time, so anything you’re repetitively testing can give you unexpected results. Static data provides consistency.
Generally, it’s better to load a small, representative set of test data into your Developer and Developer Pro sandboxes. When functionality changes unexpectedly, it’s easier to pinpoint where the problem occurred when the data is static. Developer and Developer Pro sandboxes also have a shorter refresh cycle.
If you’re loading large sets of data, you can use the Force.com Bulk API. The Bulk API and supporting web interface allows you to upload and create import jobs, monitor and manage jobs, and receive notifications when the jobs complete. For more information, see Loading Large Data Sets with the Force.com Bulk API.
Anyone with a production login can log in to a sandbox. Although most users in the production org probably aren’t aware of the existence of a sandbox, you probably don’t want them poking around your development environment either. To manage access, you can deactivate production users in sandbox. That works out well, because the deactivated production users make room for developers, who usually don’t have a login to the production system, but need a login to sandbox. This user license trading is necessary, because you have a finite number of licenses.
The easiest way to give developers a login to sandbox is to create them as users in production, but don’t activate them until needed. After creating or refreshing a sandbox, deactivate production users who don’t need access and then activate the developer users. Just make sure that the user you deactivate in sandbox isn’t someone who logs in to that environment.
All licenses are copied from production to sandbox. If a new license is applied in production and you want to apply it to sandbox, you must refresh with the sync tool (see Match Production Licenses to Sandbox without a Refresh ). If you don’t refresh, you can lose your work.
When you create a sandbox, all email addresses, except the sandbox creator, are modified so that people don’t receive emails from sandbox testing. Note that email delivery defaults to off, so if you need to test automated emails from Apex or workflow rules, you must turn this setting on. Not only are emails not sent, but unit tests fail when Messaging.sendEmail throws exceptions.
Here are some tips: