Skip to content

Quality gates

13 guides

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.

TopicReference
Release-owner GitHub, package, promotion, and publication stepsManual release-owner checklist
Repeatable passing, failing, skipped, and unable Check outcomesCheck and Check Set outcome verification
Scratch org ownership, reuse, cleanup, and release allocationScratch org lifecycle and release plan
Package validation and upgrade behaviorPackage testing and upgrades
Fail-closed release runtime matrixRelease runtime matrix
Reviewed static-analysis exceptionsCode Analyzer suppressions
Documentation requirementsDocumentation standard
Generated HTML, screenshots, and visual verificationStatic-site rendering and visual verification
Test-only Apex access and architecture enforcementApex test-only access
Product-neutral data-shape and execution-context evidencePlatform conformance
Display-budget fallback fixture and verification stepsVerify shared display-budget fallback
Regression tests required for every behavior changeWrite code with verifiable outcomes
Completing or retiring a local feature specificationSpecification lifecycle