gsd-add-tests

To automate test generation for completed features, you can use a skill that analyzes your implementation files and project documentation to automatically generate unit and e2e tests. It classifies files into testing categories and presents a structured plan for approval.

Automated test suite creation based on UAT criteria is needed after finishing a feature implementation. It eliminates manual boilerplate by verifying generated tests against project requirements and ensuring full coverage using existing project specifications.

RED-GREEN verification in automated testing workflows ensures generated tests follow standard conventions by initially failing (RED) and then passing (GREEN) against project requirements. This mechanism validates that your generated test suite accurately reflects the intended implementation context.

Yes, automated test generation requires integration with project planning files like SUMMARY.md and CONTEXT.md. Analyzing these existing implementation context files ensures the generated unit and end-to-end tests align with your documented UAT criteria.

The best way to generate e2e tests without manual boilerplate is to automate the process using implementation context and documentation. A structured approach analyzes completed development phases to classify files and automatically output the required test suite.

Yes, you can classify implementation files into TDD or E2E categories automatically. The automation analyzes your completed development phases, categorizes the files accordingly, and presents a structured test generation plan for your approval.