tdd-workflow

To enforce test-driven development, this workflow mandates writing unit, integration, and E2E tests before implementing code. It guides you through outlining user journeys, generating tests, and running them to ensure strict test-first execution and prevent regressions.

The minimum test coverage required to prevent regressions is 80% or higher. This threshold is strictly mandated across unit, integration, and end-to-end tests during feature creation, bug fixes, and refactoring to ensure high-quality code.

To apply TDD workflows when refactoring, the process enforces writing and validating tests with defined thresholds before modifying code. This structured workflow includes safety checks to ensure refactoring does not break existing user journeys or drop coverage below 80%.

Yes, you can use this workflow for integration and E2E testing with Playwright. It explicitly supports unit, integration, and end-to-end testing, ensuring comprehensive test coverage is generated and validated across all these testing layers.

The best way to structure unit tests is to first outline a user journey for the new feature, then generate corresponding test cases. This structured workflow ensures tests are written and validated before any feature code is implemented.