Release Readiness

A single go / no-go verdict for a release, computed from your latest test signals — pass rate, coverage, open bugs, regressions, and security findings — against a policy you define.

What it answers

Release Readiness rolls the state of a project up into one question: is this build safe to ship? Instead of asking each team to eyeball separate dashboards, it evaluates the latest run against a configurable gate policy and returns a clear verdict: Ready, At Risk, or Blocked.

Signals

The readiness verdict aggregates signals that VigilQA already tracks:

Signal	Source	Typical gate
Pass rate	Latest test run	≥ 98%
Requirement coverage	Traceability / CoverageGap	≥ 90%
Open Critical / High bugs	Bug Tracker	0
New regressions	RegressionGuard	0
Flaky ratio	FlakyDetector	< 2%
Critical security findings	Security & VAPT	0

Gate policy

Each project defines a readiness policy. Any signal can be a hard gate (a single breach blocks the release) or a soft gate (it degrades the verdict to At Risk but does not block). Policies live in config so they are versioned with your project.

release_readiness:
  policy:
    - signal: pass_rate
      min: 0.98
      gate: hard
    - signal: requirement_coverage
      min: 0.90
      gate: hard
    - signal: open_bugs
      severity: [critical, high]
      max: 0
      gate: hard
    - signal: new_regressions
      max: 0
      gate: hard
    - signal: flaky_ratio
      max: 0.02
      gate: soft
    - signal: security_findings
      severity: [critical]
      max: 0
      gate: hard

The readiness report

Open Release Readiness in the dashboard to see the current verdict, each signal with its measured value versus its gate, and the exact items that are blocking — the failing tests, the open Critical bugs, the regressed cases. Every blocker links straight to its detail so the owner can act. The full report exports to PDF for release sign-off and audit trails.

Gating CI/CD

Readiness can gate a deploy. Add the readiness check as a step in your pipeline; it exits non-zero when the verdict is Blocked, stopping the deploy job before it runs.

# GitHub Actions example
- name: Release readiness gate
  run: vigilqa readiness check --project myapp --fail-on blocked