tdd-workflow

Test-driven development for API endpoints and UI components is enforced by mandating failing tests be written before implementation, followed by writing minimal code to pass them. This ensures reliable automated test suites and prevents regressions.

The required test coverage threshold for JavaScript and TypeScript projects is 80% or higher combined coverage across unit, integration, and E2E tests. CI pipelines must run coverage checks to enforce this standard.

Mocking external services like Supabase, Redis, and OpenAI in integration testing requires using specific patterns to isolate dependencies. This keeps your tests deterministic, fast, and reliable by preventing external network calls.

Yes, you can use Playwright for E2E testing when refactoring code. The workflow requires comprehensive E2E tests alongside unit and integration tests to ensure refactors remain safe and maintain an 80%+ coverage threshold.

The best way to fix complex bugs using a test-first workflow is to write a failing test that reproduces the exact bug, then implement the minimal code fix to make the test pass, ensuring the regression is permanently covered.

Yes, you need unit, integration, and E2E tests for every new feature to meet the 80%+ combined coverage requirement. This comprehensive testing strategy ensures features are delivered with reliable automated tests and measurable coverage.