gsd-add-tests

To generate unit and end-to-end tests for a completed phase, provide the phase's SUMMARY.md, CONTEXT.md, and VERIFICATION.md artifacts. The system creates an implementation-aware test plan, classifies files, and applies RED-GREEN validation before committing coverage.

RED-GREEN validation in phase test generation ensures newly created tests initially fail (RED) before implementation fixes are applied to make them pass (GREEN). This workflow gate verifies that tests accurately reflect acceptance criteria before committing coverage.

Test classification workflows separate unit tests from end-to-end tests by evaluating implementation files against the phase context. Files are categorized into unit, browser-based end-to-end, or skip categories, ensuring each test is placed in the correct testing layer.

Yes, you can use phase SUMMARY.md and VERIFICATION.md artifacts to plan tests automatically. The system reads these documents to build an implementation-aware test plan that aligns with your acceptance criteria and phase context without manual planning.

Automated test generation for phase-based development requires deterministic inputs and strict approval checkpoints at classification, test-plan, and gap reporting stages. It is limited to completed phases and cannot generate tests for incomplete or undocumented workflows.

Test generation workflows require approval checkpoints to keep the process controlled and auditable. Reviewing the proposed test plan, classification, and gap reporting before writing tests ensures the generated unit and end-to-end suites match implementation quality expectations.