Code Coverage Settings

The Code Coverage Settings page allows you to configure how Revvy measures and validates Apex test coverage across your Salesforce orgs.

Overview

Salesforce requires a minimum of 75% code coverage for Apex classes, Flows and triggers before deployment to production. Revvy extends this capability by letting you:

• Define coverage thresholds per org or project.

• Control whether deployments should proceed or block based on coverage.

• View historical and real-time code coverage reports.

Configurations

From the Settings tab of a connection, you can configure the following:

• Coverage Threshold (%): Set the minimum percentage (e.g., 75% or higher) required for deployment.

• Enforcement Mode:

  • Strict Mode → Block deployments if coverage is below threshold.

  • Advisory Mode → Allow deployments but show warnings.

• Scope Options:

  • Org-Wide → Applies globally to all Apex code.

  • Component-Specific → Coverage validated for only the classes/flows/triggers included in a deployment.

Use Case

Imagine your team is preparing to deploy a new custom billing engine to production. You want to ensure all Apex classes meet Salesforce’s 75% coverage rule and that no untested code sneaks through.

• With Code Coverage Settings enabled in Revvy, you set the threshold at 95% and enforce Strict Mode.

• During deployment, Revvy checks the retrieved test results. If coverage falls below 95%, the deployment is blocked automatically.

• This prevents incomplete or risky code from reaching production, reducing the chance of post-deployment failures.

This way, your DevOps enforces continuous quality while aligning with Salesforce’s compliance rules.