Quality gates
Find the checks that a change to Record Health Check must pass before it is accepted or released: outcome verification, regression tests, scratch-org use, package and upgrade testing, the release runtime matrix, static analysis, and the documentation standard. Configuring Checks in an org does not require any of them.
| Topic | Reference |
|---|---|
| Release-owner GitHub, package, promotion, and publication steps | Manual release-owner checklist |
| Repeatable passing, failing, skipped, and unable Check outcomes | Check and Check Set outcome verification |
| Scratch org ownership, reuse, cleanup, and release allocation | Scratch org lifecycle and release plan |
| Package validation and upgrade behavior | Package testing and upgrades |
| Fail-closed release runtime matrix | Release runtime matrix |
| Reviewed static-analysis exceptions | Code Analyzer suppressions |
| Documentation requirements | Documentation standard |
| Generated HTML, screenshots, and visual verification | Static-site rendering and visual verification |
| Test-only Apex access and architecture enforcement | Apex test-only access |
| Product-neutral data-shape and execution-context evidence | Platform conformance |
| Display-budget fallback fixture and verification steps | Verify shared display-budget fallback |
| Regression tests required for every behavior change | Write code with verifiable outcomes |
| Completing or retiring a local feature specification | Specification lifecycle |