tdd-workflow

Enforces test-driven development with unit, integration, and Playwright E2E tests.

Updated Feb 5, 2026

Search Tags:#tdd #playwright #unit-testing #integration-testing #e2e-testing #test-driven-development #test-coverage

Ready to run

npx skills add https://github.com/gugug168/claudecode-tutorial --skill tdd-workflow-gugug168

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/gugug168/claudecode-tutorial/tree/main/everything-claude-code-learning/02-Skills/tdd-workflow
Command: npx skills add https://github.com/gugug168/claudecode-tutorial --skill tdd-workflow-gugug168

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures development produces reliable, tested code by embedding test-driven development practices into the feature, bugfix, and refactor workflow so regressions are caught early and confidence in changes increases.

Core Features & Use Cases

TDD-first workflow: Write failing tests before implementation to drive design and correctness.
Multi-layer testing: Enforce unit, integration, and Playwright E2E tests to validate behavior from function to full user flows.
Coverage & quality gates: Require at least 80% combined coverage, mock external dependencies, and validate edge and error scenarios.
Use case: Implement a new API endpoint by authoring failing integration tests, implement the endpoint to satisfy tests, add unit tests for core logic, and cover end-to-end flows with Playwright.

Quick Start

Write failing tests that express the desired user journey, implement code to make them pass, run the test suite, and verify coverage meets or exceeds 80%.

Frequently Asked Questions about tdd-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I start test-driven development for a new API endpoint?▼

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.

What is the best way to enforce 80% test coverage during refactoring?▼

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.

Does this TDD workflow support Playwright E2E testing?▼

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.

How do I write failing tests first for bug fixes?▼

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%.

Why mock external dependencies in integration testing?▼

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.

Can I use unit testing and integration testing together in this TDD workflow?▼

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.