retrospective-validation

Measuring validation effectiveness involves analyzing historical validation runs, git deploy history, CI/CD logs, and incident post-mortems to calculate false pass/fail rates, revert frequency, and a confidence score.

A false pass rate in retrospective validation analysis quantifies the frequency of deployments that passed validation checks but subsequently triggered incidents or required reverts, revealing gaps in test coverage.

Calculating revert frequency and evidence quality requires aggregating past validation reports and incident post-mortems to correlate deployment outcomes with validation gaps, ultimately producing a quantitative confidence score.

Yes, retrospective validation analysis directly ingests existing git deploy history, CI/CD build logs, and validation reports to map incidents to validation gaps and compute quantitative effectiveness metrics.

Mapping incident post-mortems to validation gaps is best achieved by aggregating historical evidence and deployment outcomes to identify recurring patterns, compute a confidence score, and generate actionable process recommendations.

The retrospective validation report uses a structured format stored in the e2e-evidence/retrospective/ directory, containing quantitative metrics, correlation analyses, and a computed confidence score.