tdd

Apply test-driven development with red-green-refactor cycles and behavior-focused tests.

Updated Jun 26, 2026

Search Tags:#testing #tdd #software development #integration tests #red-green-refactor #mocking

Ready to run

npx skills add https://github.com/yash-garg/pi-config --skill tdd-yash-garg

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/yash-garg/pi-config/tree/main/skills/tdd
Command: npx skills add https://github.com/yash-garg/pi-config --skill tdd-yash-garg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers avoid fragile implementations by guiding them to build and validate software behavior through test-driven development cycles.

Core Features & Use Cases

Behavior-focused testing: Encourages integration-style tests that verify public interfaces instead of implementation details.
Red-green-refactor workflow: Guides incremental development through small test-first iterations, minimal implementations, and safe refactoring.
Use Case: When adding a feature or fixing a bug, use this Skill to define the expected behavior, write a failing test, implement the smallest solution, and improve the design afterward.

Quick Start

Use the tdd skill to help me implement this feature using a red-green-refactor workflow with behavior-focused tests.

Frequently Asked Questions about tdd

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

FAQPage Schema

What is test-driven development and how does the red-green-refactor cycle work?▼

Test-driven development is a test-first practice where you write a failing test, implement the minimal code to pass it, and then refactor safely. This red-green-refactor cycle builds reliable software through incremental, behavior-focused iterations.

How do I write behavior-focused integration tests for a new feature?▼

To write behavior-focused integration tests, validate public interfaces and expected outcomes rather than internal implementation details. Define the desired behavior first, write a failing test, then implement the smallest solution to make it pass.

When should I use mocking in integration tests?▼

Mocking in integration tests should be used to define boundaries around external dependencies. By mocking these boundaries, you ensure your behavior-focused tests remain reliable and validate your public interfaces without coupling to fragile implementation details.

What is the best way to fix a bug using a test-first development workflow?▼

The best way to fix a bug using test-first development is to write a failing test that reproduces the exact behavior issue. Once the test fails, implement the smallest fix to make it pass, then refactor the code to improve maintainability.

Does test-driven development work for fixing bugs and adding features incrementally?▼

Yes, test-driven development works for both bug fixes and feature development by enforcing incremental changes. You define expected behavior upfront, write a failing test, and apply the red-green-refactor cycle to ensure reliable public interfaces.

Why do my tests break when I refactor my code?▼

Tests break during refactoring when they are coupled to implementation details rather than public interfaces. Behavior-focused testing prevents this by validating expected outcomes through integration tests, allowing you to refactor internal code safely.