tdd-workflow

Enforce TDD by writing tests before implementation, categorizing into unit, integration, and E2E tests, and maintaining 80%+ coverage. Follow a step-by-step playbook defining journeys, generating tests, failing fast, implementing, refactoring, and verifying coverage.

Structure tests by using Vitest for unit and integration testing, and Playwright for E2E testing. Define user journeys first, generate corresponding tests across these categories, then implement minimal code to satisfy them.

Yes, TDD requires a minimum 80% test coverage threshold. This includes edge-case coverage and clear failure handling to ensure guardrails are maintained across all unit, integration, and E2E test suites.

Start the TDD workflow by defining a user journey and writing corresponding tests. Run the suite to fail fast, implement minimal code to satisfy the tests, then iterate until 80%+ coverage is achieved.

The 80% coverage TDD workflow is explicitly designed for creating features, fixing bugs, refactoring, adding API endpoints, or creating components. It may not be suitable for exploratory prototyping or throwaway scripts where strict coverage guardrails are unnecessary.

Writing tests before implementation ensures the test suite fails fast initially, guiding developers to write minimal code that satisfies the tests. This enforces the TDD practice and maintains strict edge-case coverage and failure handling throughout development.