Lesson 27 of 29
In Progress

Copado

Introduction

In this lesson, you will learn how to integrate Quality Clouds with Copado to ensure that code quality is automatically validated throughout your Salesforce DevOps pipeline.

By connecting Quality Clouds to Copado, every commit linked to a user story can be scanned for coding standards and best practices. This allows teams to detect issues earlier, reduce technical debt, and ensure that only high-quality code moves forward in the release process.This integration also introduces the Release Tracker, which provides a centralized view of scan coverage and quality status across Copado releases.

Why Integrate Quality Clouds with Copado?

Integrating Quality Clouds with Copado helps teams bring automated quality control directly into their DevOps workflow.

Instead of running manual scans at the end of development, quality checks happen automatically as developers work on their user stories.

• Detect issues earlier in development
• Reduce manual code reviews
• Enforce coding standards automatically
• Improve release quality and stability
• Gain visibility into quality across releases

By embedding quality checks into the development pipeline, organizations can deliver Salesforce changes faster while maintaining strong governance.

What is Copado?

Copado is a DevOps platform designed specifically for Salesforce development. It helps teams manage and automate the full application lifecycle, including:

• Development
• Testing
• Release management
• Deployment

By integrating Quality Clouds with Copado, teams can automatically analyze their code during this process and ensure compliance with coding standards before changes are promoted.

The Release Tracker

The Release Tracker provides a centralized view of quality across Copado releases.

It allows Release Managers and teams to monitor which user stories have been scanned and whether they meet quality standards. With Release Tracker, you can:

• View all user stories linked to a release
• Monitor Quality Gate status
• Identify items that have not been scanned yet
• Launch scans for multiple user stories at once
• Detect potential quality blockers before deployment

This helps teams ensure that every item included in a release has been properly validated.

Running Quality Clouds Scans

Once the integration is configured (you can you review the integration steps in this article), scans can run automatically or manually.

Automatic Scans

Automatic scans run whenever new changes are committed to a user story whose repository is connected to Quality Clouds. This requires Quality Gates to be enabled.

Automatic scans allow teams to detect issues early, before code is promoted.

Manual Scans

Developers can also launch scans directly from the user story. To run a scan manually:

  1. Open the user story.
  2. Click Run Quality Clouds Scan Flow.
  3. The scan will analyze the branch associated with the story.

This allows developers to validate their code quality at any time during development.

Enforcing Quality with Quality Gates

Quality Gates ensure that code meets defined standards before it progresses through the pipeline. When a user attempts to Submit Changes in Copado:

• The system verifies whether a Quality Clouds scan has been executed after the latest changes.
• The scan must pass all configured Quality Gates.

If the scan fails the Quality Gates, the promotion is blocked.

If Quality Gates Fail

If a user story fails the Quality Gates, developers have two options:

Fix the issues in the code and run the scan again.
Request a write-off if the issue is accepted by the organization’s governance policy.

This ensures that quality standards are consistently enforced across the development lifecycle.

Key Takeaway

By integrating Quality Clouds with Copado, organizations can move from manual quality checks to automated governance.

This integration helps teams detect issues earlier, maintain coding standards, and ensure that every release meets quality requirements before deployment.