Testing Templates¶
Purpose¶
These templates support ES-109 — Testing and Verification.
Use this family after ES-108 integration has completed. ES-109 determines whether the integrated system satisfies requirements, preserves guardrails, handles defects responsibly, verifies AI-related behavior where applicable, and produces enough evidence to support ES-110 release readiness.
Recommended workflow¶
Integration Readiness Summary
↓
Test Strategy
↓
Test Plan
↓
Test Cases
↓
Verification Matrix
↓
Test Execution Record
↓
Defect Log
↓
Guardrail Verification
↓
AI Verification Record
↓
Regression Check Record
↓
Testing Readiness Summary
↓
ES-110 Release Readiness
Copy location¶
Do not edit the reusable templates directly. Copy completed project versions into:
docs/project-workspace/testing/
Template set¶
Test Strategy
Define approach, source evidence, verification priorities, guardrails, AI position, and risks.
02Test Plan
Define scope, ownership, execution plan, entry/exit criteria, environments, data, and evidence.
03Test Cases
Define test cases with requirements, guardrails, steps, expected results, and evidence.
04Verification Matrix
Map requirements, guardrails, risks, and defects to methods, results, evidence, and gaps.
05Test Execution Record
Record execution, results, failed tests, blocked tests, and retest needs.
06Defect Log
Track defects, severity, owners, resolution, retest, accepted risks, and status.
07Guardrail Verification
Verify architecture, design, access, evidence, security, privacy, AI, and operational guardrails.
08AI Verification Record
Verify AI boundaries, human review, fallback, rejection paths, prohibited data, and AI gaps.
09Regression Check Record
Record regression checks, failures, gaps, and confidence for previously verified behavior.
10Testing Readiness Summary
Summarize verification results, open defects, risks, gaps, and readiness for ES-110.
Do not treat ES-109 as a list of tests run. Testing is useful only when it verifies requirements, guardrails, risks, AI boundaries, evidence behavior, and release implications.
In ETIS, testing produces decision-quality evidence. A passed test is not just a green check; it is part of the argument that the system is ready to move toward release.