tdd-workflow

Enforce test-driven development by applying a structured workflow that requires writing tests before implementation. This approach guides you to define user journeys, run tests, write code, and refactor, ensuring comprehensive coverage across features, bugs, and refactors.

The workflow for writing tests before implementation involves a guided sequence: define user journeys and write tests first, run the tests, implement the code to pass those tests, and finally refactor for clarity while verifying coverage.

Yes, the TDD workflow supports Playwright for end-to-end testing. It incorporates Playwright-based E2E testing patterns and best practices to ensure reliable QA pipelines alongside your unit and integration tests.

Yes, you can use this to generate unit, integration, and end-to-end tests together. It enables you to define user journeys and generate a comprehensive test suite that covers multiple test types within a single guided workflow.

When using a TDD workflow, you should target 80% or higher test coverage. The process includes guardrails and verification steps to ensure your codebase maintains rigorous quality and maintainability standards across all testing types.

Write tests before code when fixing bugs or building features to increase quality and maintainability. This structured approach ensures your implementation is guided by comprehensive test suites, preventing regressions and clarifying requirements upfront.