ES-109 Activities¶
Purpose¶
This page guides testing and verification work for ES-109.
Complete these activities for each integrated baseline or release candidate. Iterate when test results reveal defects, gaps, or unverified guardrails.
Activity 1 — Define test strategy¶
Create:
docs/testing/test_strategy.md
Use:
template-library/testing/test_strategy.md
Define testing scope, verification priorities, test levels, guardrail focus, AI verification position, and known risks.
Testing strategy evidence.
Activity 2 — Create test plan¶
Create:
docs/testing/test_plan.md
Use:
template-library/testing/test_plan.md
Define what will be tested, who owns testing, when it occurs, and what evidence is expected.
Testing plan evidence.
Activity 3 — Define test cases¶
Create:
docs/testing/test_cases.md
Use:
template-library/testing/test_cases.md
Define functional, non-functional, guardrail, failure-path, AI-boundary, and regression test cases.
Test case evidence.
Activity 4 — Build verification matrix¶
Create:
docs/testing/verification_matrix.md
Use:
template-library/testing/verification_matrix.md
Map requirements, guardrails, risks, and findings to verification evidence.
Verification traceability evidence.
Activity 5 — Execute tests and record results¶
Create or update:
docs/testing/test_execution_record.md
Use:
template-library/testing/test_execution_record.md
Record test execution, results, evidence, failures, and retest status.
Test execution evidence.
Activity 6 — Maintain defect log¶
Create or update:
docs/testing/defect_log.md
Use:
template-library/testing/defect_log.md
Record defects, severity, source, owner, resolution, retest result, and remaining risk.
Defect evidence.
Activity 7 — Verify guardrails¶
Create or update:
docs/testing/guardrail_verification.md
Use:
template-library/testing/guardrail_verification.md
Verify high-priority guardrails directly.
Guardrail verification evidence.
Activity 8 — Verify AI behavior¶
Create or update:
docs/testing/ai_verification_record.md
Use:
template-library/testing/ai_verification_record.md
If AI is not used, state not applicable and confirm no AI path exists. If AI is used, verify AI-control boundaries.
AI verification evidence.
Activity 9 — Run regression checks¶
Create or update:
docs/testing/regression_check_record.md
Use:
template-library/testing/regression_check_record.md
Record regression checks for core behavior and guardrails after integration.
Regression evidence.
Activity 10 — Complete testing readiness summary¶
Create:
docs/testing/testing_readiness_summary.md
Use:
template-library/testing/testing_readiness_summary.md
Summarize readiness for ES-110.
Transition evidence from testing to release readiness.
Recommended working order¶
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
AI may suggest failure-path tests, map requirements to missing test cases, review the verification matrix for gaps, and identify guardrail-sensitive behavior not covered by tests. Engineers decide adequacy.
Do not skip defect logging for issues fixed quickly. Fast fixes still leave useful evidence.