Stage the changes and run regression tests in a Full sandbox.
After you have made all your changes based on the integration testing, the next step is to stage the changes in a Full sandbox. The process of deploying changes to the Full sandbox is similar to the process you used to deploy changes to your Developer Pro sandbox. This phase includes regression testing and mimics how you release the changes to production.
These steps provide the high-level work flow.
Authorize the Full sandbox.
(Optional) If you made any changes based on your testing in the Developer Pro sandbox, create a release artifact (.zip). If not, use the existing release artifact.
To validate the deployment without saving the components in the target org, run all local (regression) tests. A validation enables you to verify the results of tests that would be executed during a deployment, but doesn’t commit any changes.
1sf project deploy validate --manifest manifest/package.xml --target-org full-sandbox --test-level RunLocalTestsTest the actual production deployment steps in the staging sandbox. Set up the same quick deploy that you plan to execute against the production org.
1sf project deploy validate --manifest manifest/package.xml --target-org full-sandbox --test-level RunSpecifiedTestsThis command returns a job ID that you reference in the quick deploy.
Next, test the quick deploy using the job ID returned in the previous step.
1sf project deploy quick --target-org full-sandbox --job-id jobIDAfter you validate a deployment, you have 10 days to perform the quick deployment to production.
j