gsd-add-tests

You can automate test generation by providing UAT criteria and implementation specifications for a completed phase. The system classifies implementation files into TDD, E2E, or Skip categories and presents a test plan for approval before generating RED-GREEN convention tests.

RED-GREEN testing is a test-driven development convention where RED indicates a failing initial test and GREEN indicates the passing implementation. Automated test generation applies this by structuring generated test code to follow these RED-GREEN conventions natively.

To generate a test plan, the system evaluates your completed phase's UAT criteria and implementation specifications. It categorizes implementation files into TDD, E2E, or Skip buckets and presents the proposed test plan for your review and approval before code generation begins.

Automated test analysis classifies implementation files by evaluating them against your UAT criteria and implementation specifications. It determines which files require unit-level TDD tests, which need E2E tests, and which to Skip based on the completed phase requirements.

No, once the test plan is approved, the system automatically generates the unit and E2E tests for the completed phase. The generated tests adhere to the RED-GREEN conventions, ensuring clear and maintainable code without requiring manual coding.

You should skip test generation when the automated analysis classifies specific implementation files into the Skip category. This indicates the files do not meet the criteria for TDD or E2E tests based on the provided UAT criteria and phase specifications.