Video explanation

From 00:00 to 03:41 → Full Story Lifecycle of a successful scenario

From 03:41 to 04:33 → Show a failed scenario

Written Steps

1. Commit the changes through the Commit quick action
2. If you have done Apex changes or other changes that require Apex test coverage (i.e Flow changes)
   1. Add the tests class, where either
      1. commit the apex classes (if these are modified) through the standard commit
      2. if the apex classes just need to provide coverage but no tests are added/modified, add them through the "Add apex tests button"
   2. Run the tests, using the Manage Apex Tests button
3. Validate the changes, through Validate Changes button. This will create a new validation deployment. Some important points:
   1. If you get a conflict error during the deployment, go to the created validation promotion record (in the User Story "Deliver" section), and click on "Review merge conflicts". Note that profile conflicts are set to be automatically resolved and won't be displaying.
      
   2. IMPORTANT: The changes of any conflict solved automatically by Copado will also display in this Pull Request. Reason why it's very important to review it, to ensure correct changes (for example in profiles).
   3. If the validation fails, check the error in the validation deployment (in the User Story "Deliver" section you have the promotion record and inside of it the deployment record), perform the necessary commits to fix it, and then trigger a new validation.
   4. If the validation works, create a pull request from the latest validation deployment
      
      
      
      
      
   5. After the Pull Request is approved, you can deploy the user story. Use the Guided Deploy quick action. This will provide you the link to the created promotion and as well will make sure all required actions* has been done correctly (like the validation). Note: You can see an example of a failed deploy in the video above, where the deployment was attempted without previous validation (03:41).
      
      
      
      

* Required actions to have a successful guided deploy:

1. User story is in a “Dev” org - We can add DEV to envs for check

2. User has the “Copado Admin lite” permission set or “Copado Admin” (RM)

3. There is no “Full profile and perm set” commit - If there is, ask the developer to contact the RM before deployment

4. If you have added Apex code, ensure to add the Apex Tests classes, and ensure that the minimum coverage is met by running these tests.

5. If any manual task, inform the user it has to be tracked in the generated promotion’s deployment. Guide the user.

6. User story has a successful validation deployment after the last commit.

Examples

- https://syensqo-icare.lightning.force.com/lightning/r/copado__User_Story__c/a7ZPH0000001mCH2AY/view (standard deployment)

- https://gitlab-sco.solvay.com/solvay-it-sfdc/sfdcsppcopadobuildmain/-/merge_requests/new?merge_request%5Bsource_branch%5D=promotion/P08616-DeployP08616Bugfix6&merge_request%5Btarget_branch%5D=bugfix (retrofit)