tdd-workflow

Enforce a TDD workflow by writing failing tests first, implementing minimal code to pass them, then refactoring while validating a minimum 80% coverage threshold across unit, integration, and e2e tests.

Maintain 80% test coverage during refactoring by running the verification workflow step immediately after implementation, ensuring all existing unit, integration, and end-to-end tests still pass before finalizing code changes.

The best way to write failing tests for API endpoints is to define expected integration and end-to-end behaviors upfront using your testing framework, establish the 80% coverage baseline, and then implement the API logic to satisfy those tests.

Yes, you can use Playwright for e2e testing within a TDD workflow by writing Playwright failing tests first to define user interaction scenarios, then implementing the feature code to pass them while maintaining the required coverage.

Test-driven development works for both new features and component development by requiring you to write failing tests before implementation, ensuring all code paths meet the strict 80% coverage threshold across all test levels.

You should not use a strict 80% test coverage TDD workflow for rapid prototyping or exploratory coding where immediate functional output is prioritized over comprehensive unit, integration, and e2e test validation.