Finding guide
Apex test coverage under 75%
Salesforce won't deploy Apex to production while the org's overall test coverage is under 75%, and every trigger needs at least some coverage. Low coverage usually goes unnoticed until the day an urgent fix can't be deployed.
By VanguardOps, written by a Salesforce architect with 13+ years in enterprise orgs. Updated November 17, 2026.
Why it matters
- A deployment that includes Apex fails if org-wide coverage is under 75%, so one urgent fix can be blocked by tests nobody wrote years ago.
- A trigger with no test coverage fails deployment on its own.
- Failing tests block deployments too, and they often hide real bugs.
- Code saved on old API versions behaves the way Salesforce worked years ago, and the oldest versions have been retired.
How to check your org by hand
- In Setup, open Apex Classes and use Estimate your organization's code coverage.
- In the Developer Console, run all tests and read Overall Code Coverage, then sort classes and triggers by coverage.
- Look for any trigger at 0%.
- On Apex Classes and Apex Triggers, add the API Version column and note anything far behind the current release.
How to fix it
- Start with triggers at 0%: one test that fires each trigger clears the deployment blocker.
- Then write tests for the least-covered classes that change most often. Coverage on code nobody touches buys little.
- Fix or delete failing tests before adding new ones.
- Move code on old API versions forward in a sandbox and rerun all tests before deploying.
What VanguardOps flags
A scan checks this from metadata with fixed rules, never by reading records:
- Org-wide Apex coverage under 75%: a high finding, listing the classes and triggers under 75%, lowest first.
- Any Apex trigger with no test coverage: a medium finding.
- Apex tests that failed on their most recent run in the last 30 days: a high finding.
- Apex saved on a retired API version (30.0 or older), and Apex on API versions about five years old or more.
Common questions
- What Apex test coverage does Salesforce require?
- At least 75% across all Apex in the org to deploy to production, and every trigger must have some coverage. Each test must also pass. Check Salesforce's deployment documentation for the current rules.
- Is 75% coverage good enough?
- It's the minimum to deploy, not a measure of quality. Tests that run code without asserting results raise coverage and catch nothing. Aim for meaningful assertions on the code that changes most.
- Why did coverage drop when I didn't change any code?
- Coverage is recalculated when tests run. Deleted tests, newly failing tests, or data a test depended on can all lower it. Run all tests and compare class by class.