Changing Organization Settings (Code Coverage)
Written for the Old UI
This article was written for the old UI. The instructions are still usable, but the screenshots are outdated. In some cases, items referenced in the instructions have moved or changed. If you cannot find an item, see the Where Did It Go article.
Overview
Explore the Settings tab of an Organization to manage its Code Coverage and Vlocity component inclusion. This article provides information about Code Coverage and detailed instructions on adjusting these settings.
DevOps Code Coverage
Salesforce mandates at least 75% code coverage for Apex classes, Flows, and triggers before production deployment. The Code Coverage setting in Cloud DevOps lets you specify a custom code coverage range of 75%-95% for deployments to this org. When Code Coverage is enabled, deployments to this org are blocked unless your specified threshold is met.
This feature allows you to enforce strict code coverage, ensuring that only safe code is deployed to selected orgs. The instructions below show you how to enable this setting.
Use Case
Your team is ready to deploy a new custom billing engine to production. To ensure compliance with Salesforce's code coverage standards and avoid deploying untested code, you decide to set your production org to require 95% Code Coverage.
Flosum Cloud DevOps will test your code coverage during deployment, and if it falls below 95%, the deployment will automatically be blocked.
This prevents incomplete or risky code from reaching production, reducing the chance of post-deployment failures.
Change Settings
Last updated
Was this helpful?





