ES-109 Navigation¶
Purpose¶
This page explains how to move through ES-109 and where testing and verification artifacts belong.
ES-109 connects integration evidence to release-readiness evaluation.
ES-109 path¶
README
↓
navigation.md
↓
engineering_context.md
↓
activities.md
↓
evidence.md
↓
outputs.md
↓
readiness_gate.md
↓
stage_manifest.md
↓
ES-110
Repository areas used in this stage¶
docs/engineering/ES-109/ guidance
template-library/testing/ reusable testing templates
examples/lmu-coicp/testing/ completed reference examples
docs/testing/ project-specific testing evidence
What to copy¶
Copy templates from template-library/testing/ into docs/testing/, then complete them for your project.
Do not edit the original templates.
Expected project artifacts¶
docs/testing/
test_strategy.md
test_plan.md
test_cases.md
verification_matrix.md
test_execution_record.md
defect_log.md
guardrail_verification.md
ai_verification_record.md
regression_check_record.md
testing_readiness_summary.md
Traceability expectation¶
Every important test should connect to at least one requirement, design artifact, integrated work item, guardrail, risk, defect, or release-readiness question.
Untraceable tests may still be useful, but critical release evidence should be traceable.
Common Pitfall
Do not create a test plan that ignores known findings from ES-108. Testing should focus on the risks integration revealed.