Search⌘ K
AI Features

Verification Gates and Test Layer Selection

Learn how to select unit, contract, integration, and smoke tests for distinct CI/CD promotion decisions. Connect each check to its dependency scope, timing, failure meaning, and recorded evidence. Use immutable image digests, manifest bundles, time limits, and staging smoke results to defend safe production promotion and explain why a failure blocks increased exposure.

In a fifteen-minute design round, your judgment shows in the checks you choose: which must pass before staging, which must pass before production exposure increases, and what evidence proves that the exact artifact was evaluated. A verification gate is a promotion rule that accepts or blocks one immutable artifact based on recorded evidence. It separates a successful build from a release that is safe to expose more widely.

The artifact flow provides the structure for these decisions. Before merge, unit and contract checks give fast feedback on the proposed code. After merge, the pipeline builds one image and records its digest with the ...