tdd-workflow

Test-driven development is enforced by mandating a structured workflow of user journeys, test generation, implementation, and refactoring to achieve a minimum of 80% code coverage across unit, integration, and e2e tests.

The best way to write tests before implementation is to first define tests for expected inputs, outputs, and error conditions, then write the minimal code to pass those tests, ensuring reliability through a structured TDD workflow.

Yes, the test-driven development workflow supports Vitest and Playwright by providing specific patterns to guide test creation, implementation, and refactoring for comprehensive coverage.

To mock external services like Supabase, Redis, and OpenAI during unit testing, the workflow utilizes specific mocking patterns to isolate dependencies and ensure accurate test coverage.

TDD requires 80% code coverage across unit, integration, and end-to-end tests to guarantee high test coverage and robust software quality by mandating comprehensive validation throughout the development lifecycle.

Yes, you can use this TDD workflow for refactoring existing code without breaking functionality, as it provides clear steps for structured refactoring following comprehensive test generation and implementation.