tdd-workflow

To enforce a Test-Driven Development workflow, you must mandate test creation before code implementation. This approach guides the process through user journey definition, test case generation, implementation, and refactoring to ensure robust code.

The minimum code coverage required for unit, integration, and E2E tests is 80 percent. This threshold is enforced across all test types to guarantee high code quality and comprehensive test coverage.

To write tests first when developing a new API endpoint, begin by defining user journeys and generating test cases. Proceed with implementation only after tests are written, concluding with coverage verification.

Yes, this TDD workflow supports Playwright for end-to-end testing. It comprehensively covers unit, integration, and end-to-end test types, utilizing frameworks like Jest, Vitest, and Playwright for coverage verification.

Yes, you can use Jest and Vitest for unit and integration tests in this workflow. The testing process utilizes these frameworks alongside Playwright to enforce comprehensive testing and achieve 80% code coverage.

A limitation of enforcing strict test-first development is the mandatory overhead of writing tests before any implementation. This approach requires defining user journeys and test cases upfront, which may slow down rapid prototyping.