Engineering Stage

ES-109 — Testing and Verification

Verify that integrated implementation satisfies requirements, preserves guardrails, handles failure paths, and produces trustworthy evidence.

Verification and Release Preparation Testing Evidence Next: ES-110

StageES-109

Estimated EffortMultiple iterations

InputsES-108 integration evidence

OutputsTesting evidence package

Evidence Familydocs/testing/

← Previous Outputs

Current ES-109 — Readiness Gate

Next → Stage Manifest

ES-109 Readiness Gate

Purpose

This readiness gate verifies that ES-109 is complete and ES-110 can begin responsibly.

Release readiness should not begin until testing evidence is complete enough to support a release decision.

Completion standard

You are ready to continue when each gate is satisfied or a remaining gap has been explicitly documented and accepted.

Gate 1 Test strategy

Review Question

Is the testing strategy defined and aligned with requirements, risks, and guardrails?

Required Evidence

docs/testing/test_strategy.md

Status: ☐ Yes ☐ Needs review

Gate 2 Test plan

Review Question

Is the test plan clear about scope, owners, execution, and evidence?

Required Evidence

docs/testing/test_plan.md

Status: ☐ Yes ☐ Needs review

Gate 3 Test cases

Review Question

Do test cases cover requirements, guardrails, failure paths, and regression needs?

Required Evidence

docs/testing/test_cases.md

Status: ☐ Yes ☐ Needs review

Gate 4 Verification matrix

Review Question

Are tests mapped to requirements, guardrails, risks, and findings?

Required Evidence

docs/testing/verification_matrix.md

Status: ☐ Yes ☐ Needs review

Gate 5 Test execution

Review Question

Are test execution results recorded?

Required Evidence

docs/testing/test_execution_record.md

Status: ☐ Yes ☐ Needs review

Gate 6 Defect log

Review Question

Are defects recorded, assigned, resolved, deferred, or accepted?

Required Evidence

docs/testing/defect_log.md

Status: ☐ Yes ☐ Needs review

Gate 7 Guardrail verification

Review Question

Are trustworthiness guardrails explicitly verified?

Required Evidence

docs/testing/guardrail_verification.md

Status: ☐ Yes ☐ Needs review

Gate 8 AI verification

Review Question

If AI functionality exists, are AI boundaries verified? If AI is deferred, is that explicitly confirmed?

Required Evidence

docs/testing/ai_verification_record.md

Status: ☐ Yes ☐ Not applicable ☐ Needs review

Gate 9 Regression checks

Review Question

Are regression checks recorded?

Required Evidence

docs/testing/regression_check_record.md

Status: ☐ Yes ☐ Needs review

Gate 10 Transition readiness

Review Question

Does the readiness summary explain why ES-110 can begin?

Required Evidence

docs/testing/testing_readiness_summary.md

Status: ☐ Yes ☐ Needs review

Exit criteria

ES-109 is complete when verification evidence is sufficient for release-readiness evaluation.

Common Pitfall

Do not proceed to release readiness if major defects are unresolved and unaccepted.

Continue to Stage Manifest

Review the formal ES-109 stage contract.

Continue to Stage Manifest →