Skip to content

Testing Workspace

ETIS Project Workspace

Testing Workspace

Test strategy, plan, cases, execution, defects, AI verification, guardrails, readiness summary.

ES-109 Project Repository Testing

Purpose

Preserve verification evidence for requirements, risks, guardrails, AI boundaries, access controls, defects, and release readiness.

This directory should contain the project’s actual working artifacts for this lifecycle area. The links below intentionally point to the Template Library and, where available, the completed LMU/COICP example. Create the real project files in this directory when the project is ready to populate them.

What belongs here

Artifact Project File Name Template Completed Example
Test Strategy test_strategy.md Template Completed example
Test Plan test_plan.md Template Completed example
Test Cases test_cases.md Template Completed example
Test Execution Record test_execution_record.md Template Completed example
Defect Log defect_log.md Template Completed example
Verification Matrix verification_matrix.md Template Completed example
Ai Verification Record ai_verification_record.md Template Completed example
Guardrail Verification guardrail_verification.md Template Completed example
Regression Check Record regression_check_record.md Template Completed example
Testing Readiness Summary testing_readiness_summary.md Template Completed example

Start from templates

Working pattern

  1. Open the relevant template.
  2. Create the same-named file in docs/project-workspace/testing/.
  3. Replace template guidance with project-specific evidence.
  4. Compare the result with the LMU/COICP example when available.
  5. Record open risks, assumptions, and unresolved questions.
  6. Finish with the review or readiness artifact for this stage.

Evidence quality bar

Quality What It Means
Specific Names actual project facts, stakeholders, systems, scenarios, risks, and decisions.
Traceable Connects back to earlier stages and forward to later stages.
Reviewable Gives another reviewer enough evidence to challenge or approve the work.
Current Reflects the project’s actual state rather than old intent.
Governable Makes AI use, exceptions, risks, release posture, and limitations visible.
Workspace Rule

Create project artifacts here. Learn the artifact structure from the Template Library. Learn the completed pattern from the LMU/COICP example.

Continue to Release

Move forward when this stage has enough project evidence and a clear readiness decision.

Open Release →