shine-add-tests

You can generate unit and E2E tests by providing a phase identifier to automate test creation from SUMMARY.md, CONTEXT.md, and VERIFICATION.md files, producing a test plan and test artifacts for review and integration.

The RED-GREEN workflow for test generation involves classifying implementation files into unit, E2E, or Skip categories, creating a test plan for approval, and then producing test artifacts that follow this structured testing methodology.

Yes, automated test generation integrates with CI/CD and version control workflows by committing test artifacts with deterministic commit messaging, ensuring consistent integration of generated unit and E2E tests.

Automated test generation classifies code by analyzing implementation files and categorizing them into unit tests following TDD, E2E tests for browser testing, or Skip categories based on the phase's documentation.

Yes, to generate tests for a development phase, you need phases described by SUMMARY.md, CONTEXT.md, and VERIFICATION.md files, which provide the context and requirements for producing accurate test plans and artifacts.

Automated test generation for TDD workflows requires completed phases with proper documentation and applies classification into unit, E2E, or Skip categories, meaning it cannot generate tests for incomplete phases or phases lacking the required documentation files.