- The components have been validated successfully for the target environment within the last four days (96 hours).
- As part of the validation, all Apex tests in the target organization have passed.
- The overall code coverage in the organization is at least 75%, and Apex triggers have some coverage.
A validation is a deployment that’s used only to check the results of deploying components and doesn’t save any components in the organization. A validation enables you to view the success or failure messages that you would receive with an actual deployment. You can validate change sets or metadata components through the API or the Force.com Migration Tool.
To learn how to validate a change set, see Validating a Change Set in the Salesforce Help.
To validate components with the Force.com Migration Tool, set the checkOnly option to true in the deploy target. See Deploying Changes to a Salesforce Organization in the Force.com Migration Tool Guide.
Performing a Quick Deployment through the User Interface or the API
To perform a quick deployment, first run a validation-only deployment with Apex test execution on the set of components that you need to deploy. If your validation succeeds and qualifies for a quick deployment, you can start a quick deployment.
You can quick-deploy validated change sets and Metadata API components in the user interface. In the Deployment Status page, deploy a recent validation by clicking Quick Deploy next to your validation or on the validation’s detail page. This button appears only for qualifying validations.
Alternatively, you can start a quick deployment through the Metadata API by calling deployRecentValidation() and passing it the validation ID. Use this API call to deploy Metadata API components. This call doesn’t apply to change sets.