Free Access Salesforce Development-Lifecycle-and-Deployment-Designer New Release

The first task of the new sprint must be the deployment approval. After that, the other tasks of the sprint can be performed in the environments and Git.

Using Git, create a release branch from the develop branch. All fixes must be made in the release branch. After deployment, merge release with develop.

Commit upcoming changes to the features branch without merging into the develop branch. Deploy from the develop branch and then merge new sprint features into the develop branch.

Migrate the current code to the UAT sandbox. Begin new sprint development in the Dev sandbox. Make fixes in the UAT environment and deploy UAT for production after business approval.

A Do not execute any test classes in sandboxes andProduction.

Do not execute test classes in sandboxes and all test classes in Production.

Test classes cannot be executed in sandboxes.

Execute all test classes in sandboxes and selected test classes in Production.

If the username in the source org doesn't exist in the target org, the deployment will continue and Salesforce will automatically create the username in the target org.

User fields are ignored during metadata deployments and all such users need to be manually created in the target org before starting the deployment.

If the username in the source org doesn't exist inthe target org, the deployment will stop until the usernames are resolved or removed.

User Fields are preserved during metadata deployments and Salesforce attempts to locate a matching user in the target org during deployment.

JSTEST

ACCTEST

WebDriver Test

AuraDriver Test