Quality Gates in Copado Continuous Delivery
With Copado Continuous Delivery you can automate quality testing and create connection behaviors with quality gates to ensure all your changes are passing the relevant quality checks while moving across the different environments in your pipeline.
You can do this on a particular user story by using the Submit button on the User Story record or on a group of user stories if you deploy them all at once from the Pipeline page. Quality gates can also be applied to org-to-org metadata deployments. Therefore, if you create a standalone metadata deployment and there is a connection behavior in the destination environment of your deployment, quality gates and automations will be applied if the metadata components you are deploying match the specifications in the connection behavior.
Let’s take a look at each of these quality gates and see their main functionality and use case:
Use Case Example
Execute a group of steps (External CI, Apex or Salesforce Flow).
Execute a Checkmarx scan.
Apex Test with Validation
Executes the Git Promotion step with the Check Only checkbox enabled. You can specify the test level you want to apply when configuring the quality gate.
Test promotions that include Apex code, by specifying a test level.
Scans the metadata committed in the Git Promotion step with the specified Compliance Rule Group.
Automatically scan profiles or permission sets being promoted to identify if there are any compliance violations.
Pauses the deployment for a person to review the deployment details
The release manager reviews the deployment and marks the task as Complete if this is approved.
Pauses the deployment for a person to manually test the functionality in the source org*.
A QA tester validates that the functionality of the promoted user stories works as expected in the source org and marks the task as Complete if the test is successful.
Pauses the deployment for a person to create and review a pull request between the promotion branch and the destination branch*.
For promotions containing sensitive metadata, your team can decide to do a pull request review at the promotion level.
Executes a Selenium Test Group in the source org*.
Run a regression test in the source org to confirm that the functionality is working as expected.
Static Code Analysis
Scans the metadata committed in the Git Promotion step with the specified Static Code Analysis Settings.
Executes the Git Promotion step with the Check Only checkbox enabled. The test level is set to No Test Run.
Executes the URL callout.
Callout to an external system to run a job.
*Pull requests for the promotion branch are optional. Pull requests of the user story feature branches should also be enforced as a best practice.