Automate CI quality gates for Apex: enforce coverage, detect flakiness, run change-based suites, and speed up pipelines with selective or generated tests.
## Why CI Quality Gates Matter for Apex
Apex code lives in a shared org and test execution is a common bottleneck in Salesforce CI/CD. Quality gates—automated checks that a change must pass before merging or promotion—preserve stability, reduce production incidents, and keep overall test-suite runtime manageable.
## Designing Practical Gates for Salesforce
### Fast PR Feedback
- Run a lightweight test suite on pull requests: execute only tests that cover modified classes or a curated set of fast unit tests. Use SFDX (sfdx force:apex:test:run) with runSpecifiedTests or leverage change-based logic in your pipeline to restrict the initial test set.
- Fail fast on compilation errors and static-analysis violations (PMD, CodeScanner for Apex, LWC ESLint). Give developers quick, actionable output.
### Gate for Coverage and Behavior
- Enforce org-wide and per-feature coverage expectations. Because Salesforce requires 75% org coverage for deployment, check both the org-level metric and the coverage for changed classes. Track coverage delta to prevent regressions.
- Include functional smoke tests for critical flows that must remain intact after each change.
### Handle Flakiness and Runtime
- Detect flaky tests by tracking failure rates across runs. Automatically quarantine flaky tests into a separate suite and alert owners to fix them—don’t let flakes block merges indefinitely.
- Use retries sparingly (one quick rerun) for transient infra issues, but require fixes for recurring failures.
## Implementation Patterns for Apex Pipelines
### Multi-stage Pipeline
1. Lint & Compile: static analysis + sfdx validate metadata compilation.
2. PR Tests (Fast): run change-based or runSpecifiedTests for fast feedback.
3. Integration Tests: run a broader suite in a staged environment.
4. Full Nightly Suite: execute the entire test suite with profiling and reporting.
This staged approach balances speed and confidence—developers get quick feedback while a central pipeline ensures full-suite health on a schedule.
### Change-based Test Selection
- Use Git metadata to identify changed Apex classes, triggers, and metadata. Map affected test classes using code-owner annotations, convention-based naming, or a metadata dependency graph.
- Run only the relevant tests on PRs, and block the merge if any linked tests fail.
### Reporting and Telemetry
- Push test results to a central dashboard: test durations, failure trends, flaky test lists, and coverage deltas. Use this telemetry to optimize slow tests and improve the test selection strategy.
## Practical Tips
- Seed test data deterministically and prefer mocking external integrations.
- Keep test methods small and readable: single-assert focused tests are easier to maintain and diagnose.
- Automate generation for boilerplate tests where appropriate to speed coverage (e.g., bulk scenarios, CRUD validation).
Conclusion / Call-to-action
Implementing pragmatic CI quality gates for Apex reduces risk and accelerates delivery. Start with fast PR checks and staged gates, measure flakiness and coverage deltas, and iterate. To accelerate test creation and reduce manual test maintenance, try automating boilerplate Apex tests with a Test Class Generator integrated into your pipeline.