tdd-workflow

To enforce a test-driven development workflow, this Skill mandates writing tests before implementation and guides you through defining user journeys, edge cases, and error scenarios using Jest and Playwright. It ensures a structured TDD process for new features.

You maintain 80% code coverage by following the structured workflow that ensures comprehensive test coverage across unit, integration, and end-to-end tests. After implementing minimal code to satisfy initial tests, you verify coverage and refactor.

The best way to structure tests for API endpoints is to first define the API contract and expected responses with tests, then write the minimal code to satisfy those tests, and finally refactor and verify coverage using the TDD workflow.

Yes, test-driven development works for both unit and end-to-end tests. This Skill integrates Jest and Playwright to guide developers through writing tests first, ensuring comprehensive coverage across all testing layers before implementation.

You write tests before code to ensure high-quality, well-tested software, reducing bugs and improving maintainability. By defining expected behavior upfront through user journeys and edge cases, you enforce a rigorous test-first approach.

You should not use a strict test-first approach when rapid prototyping unproven concepts where immediate code behavior exploration is more critical than upfront test definition and enforcing 80% code coverage across all layers.