tdd-workflow

To start test-driven development for a new API endpoint, author failing integration tests that express the desired user journey, implement the endpoint to satisfy the tests, and add unit tests for core logic.

The best way to enforce 80% test coverage during refactoring is to apply a workflow that validates behavior through unit, integration, and end-to-end tests, requiring at least 80% combined coverage before changes pass.

Yes, this workflow supports Playwright E2E testing by enforcing multi-layer testing that validates behavior from individual functions to full user flows using Playwright end-to-end test scenarios.

To write failing tests first for bug fixes, author failing tests that express the desired behavior or user journey, implement the code changes to make them pass, and verify that combined coverage exceeds 80%.

Mocking external dependencies in integration testing isolates the codebase under test, ensuring that the workflow validates actual code behavior and achieves the required 80% combined coverage without external system interference.

Yes, you can use unit testing and integration testing together; the workflow enforces multi-layer testing by requiring unit tests for core logic and integration tests to validate behavior across API endpoints and components.