gsd-add-tests

To generate unit and E2E tests from phase specifications, run the add-tests workflow using the SUMMARY.md, CONTEXT.md, and VERIFICATION.md files of a completed phase to classify files and scaffold tests with RED-GREEN verification.

Automating test generation for CI pipelines involves scaffolding tests from phase specifications and committing them with standardized messages like test(phase-{N}): add unit and E2E tests, ensuring local validation and regression testing coverage.

Yes, generating tests for a completed phase requires SUMMARY.md, CONTEXT.md, and VERIFICATION.md files, which provide the implementation details and UAT criteria needed to classify files into unit tests, E2E tests, or non-testable skips.

RED-GREEN verification works by implementing a deterministic workflow with a planning gate and test plan approval, ensuring generated tests initially fail (RED) before implementation is adjusted to make them pass (GREEN) for the completed phase.

Yes, you can skip non-testable files during test generation because the workflow classifies each file from the phase context into unit tests, E2E tests, or skips them as non-testable based on the phase specifications.

Generated tests are committed to the repository using deterministic commit messages formatted as test(phase-{N}): add unit and E2E tests from add-tests command, ensuring clear tracking of automated test scaffolding for continuous integration.