tdd-workflow

To enforce test-driven development, this workflow mandates writing tests before implementation for features, bug fixes, and refactors. It guides you through defining user journeys, generating test cases, and implementing code to satisfy those tests.

Yes, this TDD workflow enforces 80%+ overall test coverage across unit, integration, and end-to-end tests. It acts as a quality gate to ensure new features and refactors adhere to strict coverage discipline.

The step-by-step TDD process involves defining clear user journeys, generating specific test cases, executing those tests, writing implementation code to satisfy the tests, and verifying that overall coverage meets the 80%+ threshold.

Yes, this TDD workflow applies to end-to-end tests, including those written with Playwright. It ensures test-first development across all testing layers, from unit and integration to end-to-end user journeys.

Writing tests before implementation code reduces defects and improves long-term maintainability. This test-driven approach provides a guided process to create tests, implement code to satisfy them, and refactor with confidence.

Enforcing an 80%+ test coverage threshold requires writing tests before any implementation code for all features, bug fixes, and refactors. This strict quality gate may slow down initial development speed to ensure long-term maintainability.