test-document-generator

Generating an evidence-grounded test plan involves mapping provided requirements, specs, and risk inputs to concrete test cases, producing a Markdown document with traceability matrices and acceptance criteria for regression scope.

Creating acceptance criteria and regression scope from a PR description requires mapping the change inputs to a test matrix. The result is a Markdown document grounding observed facts, inferences, and open questions for auditability.

An evidence-grounded test document is a Markdown artifact that separates observed facts, inferences, and assumptions from source material. It builds requirement-to-test traceability and includes execution records for delivery lifecycle auditability.

You can build a test matrix from user-provided feature descriptions without blocking. The process asks only for missing decisions materially affecting test scope, while recording smaller gaps as open questions within the Markdown output.

The generated test plan supports defect-to-fix-to-retest closure tracking by persisting execution records and closure fields directly within the Markdown test artifact, ensuring complete auditability across the delivery lifecycle.

You should not use automated test case generation from specs when you lack source material like issues or proposals, as strict source grounding is required to separate observed facts from inferences and map requirements to test cases.