gsd-add-tests

To generate unit and E2E tests from UAT specs, you use a completed phase specification including SUMMARY.md, CONTEXT.md, and VERIFICATION.md to drive an implementation-aware classification and test creation process.

RED-GREEN test generation is a workflow where tests are initially written to fail (RED) then made to pass (GREEN). It applies to phase verification by producing an approval-gated test plan before generating the actual unit and browser E2E tests.

You classify implementation files for unit testing versus browser automation by reviewing the completed implementation files alongside phase specifications, categorizing them into unit TDD coverage, browser E2E coverage, or items to skip.

Yes, you can use UAT criteria to automatically create a test plan for a completed development phase. The process analyzes your UAT expectations and implementation context to produce an actionable, approval-gated test plan before writing tests.

Limitations when generating browser E2E tests from phase specifications include relying entirely on the accuracy of SUMMARY.md, CONTEXT.md, and VERIFICATION.md files, and requiring manual approval at classification and test plan gates before test generation proceeds.

Yes, you need specific markdown files to generate tests for a development phase. The process requires completed SUMMARY.md, CONTEXT.md, and VERIFICATION.md files to serve as the source of truth for UAT expectations and implementation context.