gsd-add-tests

You can auto-generate unit and e2e tests from UAT criteria by using a GSD workflow skill that reads your phase context and verification documents to produce TDD-compliant test files. This eliminates manual test creation effort by directly mapping acceptance criteria to test logic.

To generate tests for a completed project phase, you need the phase's UAT criteria, implementation files, SUMMARY.md, CONTEXT.md, and VERIFICATION.md. These documents provide the test specifications and implementation logic required to produce valid test coverage.

Automated test generation follows RED-GREEN TDD conventions to ensure properly structured, valid tests. It produces test files that correctly validate implementation logic and align with the phase's intended functionality and acceptance criteria.

Yes, you can generate both unit tests and end-to-end tests for backend API logic. The test generation process creates matching unit tests for backend logic and E2E tests for user flows, reducing comprehensive test creation time from hours to minutes.

You should generate tests for completed GSD workflow phases when implementation is finalized and UAT criteria are available. Applying test generation at this stage ensures tests accurately match the phase's intended functionality without disrupting active development.

Manually written tests often fail to align with implementation details because they are time-consuming and inconsistent. Automating the process ensures tests are accurate, comprehensive, and directly match the phase's original UAT criteria and implementation files.