test-driven-development

Automates Red-Green-Refactor cycles with failing-first unit tests before coding.

4|Updated Mar 15, 2024

Search Tags:#tdd #red-green-refactor #code-quality #unit-tests #test-driven-development #software-testing

Ready to run

npx skills add https://github.com/izyanrajwani/agent-skills-library --skill test-driven-development-izyanrajwani

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/izyanrajwani/agent-skills-library/tree/main/skills/test-driven-development
Command: npx skills add https://github.com/izyanrajwani/agent-skills-library --skill test-driven-development-izyanrajwani

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TDD helps teams ensure software behaviors are verified by writing tests first, reducing defects and regressions.

Core Features & Use Cases

Red-Green-Refactor workflow: design tests first, implement minimal code to pass, and refactor confidently.
Behavior-driven development: align implementation with observable outcomes and user needs.
Safety through tests: establish guardrails for feature changes and refactoring across the codebase.

Quick Start

Compose a failing unit test for the desired behavior, then write the minimal code to pass it.

Frequently Asked Questions about test-driven-development

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

FAQPage Schema

How do I start writing unit tests before implementation using a red-green-refactor workflow?▼

To start test-driven development, compose a failing unit test for the desired behavior, then write the minimal code required to pass it. This red-green-refactor cycle validates outcomes before implementation proceeds.

What is behavior-driven test-first development and when should I use it?▼

Test-first development is a workflow mandating failing tests before coding to verify observable behavior. Use it for feature work, bug fixes, and refactors to reduce defects and establish safety guardrails.

Does test-driven development work for refactoring existing code safely?▼

Test-driven development works for refactoring by establishing tests that prove current behavior before changes are made. This provides measurable outcomes and safety guardrails to confidently modify code without regressions.

What's the best way to align software implementation with observable outcomes through testing?▼

The best way to align implementation with outcomes is behavior-driven development, writing tests first to define expected results. This ensures code changes are validated against measurable test outcomes incrementally.

Why do my unit tests not catch regressions when adding new features?▼

Unit tests may miss regressions if written after coding rather than using a failing-first test approach. Test-driven development mandates writing failing tests first to verify behavior incrementally and catch defects immediately.