gsd-add-tests

Automated test generation for completed phases is achieved by analyzing UAT criteria and implementation specifications to create unit and E2E tests. This approach uses the phase's SUMMARY.md, CONTEXT.md, and VERIFICATION.md files to generate the required tests automatically.

RED-GREEN conventions in automated testing dictate generating failing tests first (RED) based on UAT criteria, then aligning them with implementation specifications to ensure they pass (GREEN). This ensures the generated tests accurately reflect the completed phase's functionality.

To generate UAT criteria-based tests, you need access to the phase's SUMMARY.md, CONTEXT.md, and VERIFICATION.md files. These implementation files provide the specifications and verification details required to automatically generate accurate unit and end-to-end tests.

Yes, you can automatically generate unit and E2E tests directly from implementation specifications. By analyzing the UAT criteria and implementation files of a completed phase, the test generation process creates both unit and end-to-end tests ready for review and integration.

You need to generate tests for a completed phase when you want to automate the verification of implementation specifications and UAT criteria. This is typically done after the phase is complete, allowing you to automatically create tests that can be reviewed and approved for integration.

Automated test generation for phase testing is limited by its dependency on specific file structures; it requires access to the phase's SUMMARY.md, CONTEXT.md, and VERIFICATION.md files. Without these specific implementation files and clear UAT criteria, the test generation cannot proceed accurately.