generate-test-plan

A test plan from a feature spec requires describing the feature and its acceptance criteria. The system then produces a prioritized markdown document saved to the docs/testplans/ directory, including risk analysis and a coverage matrix.

A structured test plan includes risk analysis, a coverage matrix, and automation candidates. It formats test cases and segments testing phases to guide QA teams, saving the output as markdown in the docs/testplans/ directory.

Identifying automation candidates involves generating a structured test plan from your feature spec. The resulting document explicitly lists potential automation candidates alongside the coverage matrix and risk analysis.

Yes, you can generate a risk analysis matrix without executing tests. The process creates a markdown documentation file containing the matrix and coverage details, strictly generating QA documentation without running tests.

Yes, the test plan generator supports mappings to standard test plan templates. It produces phase segmentation and structured markdown files for reuse across different features within your QA workflows.

The limitation of generating test plans from implementation is that it only produces documentation. It does not execute tests, run automation scripts, or launch applications, serving solely to output a markdown file.