tdd-workflow

Test-driven development is enforced by strictly following the red-green-refactor cycle for every code change. You must write tests first, implement code to satisfy them, run the full test suite, and iterate until achieving 80%+ coverage.

Yes, this TDD workflow supports both unit and end-to-end tests. It provides specific templates and examples for unit and integration testing using Jest or Vitest, alongside end-to-end testing workflows utilizing Playwright.

The best way to start the red-green-refactor cycle for a bug fix is to activate the TDD workflow immediately. Write a failing test that reproduces the bug, implement the minimal code to pass it, and then refactor while maintaining 80%+ coverage.

Yes, you can use this test-driven development process with Vitest and Playwright. The workflow explicitly supports writing unit tests with Jest or Vitest and managing end-to-end tests using Playwright across your development cycle.

Writing tests first during refactoring ensures you follow a disciplined test-driven development process. This practice reduces regressions and speeds delivery by verifying existing behavior remains intact before you modify the underlying implementation.

To achieve 80% test coverage during test-driven development, write tests first and then implement code to satisfy them. Run the full test suite repeatedly and iterate on your implementation until the coverage goals are met.