test-driven-development

Enforce a Red-Green-Refactor cycle by writing failing tests before production code.

Updated May 7, 2025

Search Tags:#workflow #testing #red-green-refactor #quality-assurance #software-engineering #test-driven-development

Ready to run

npx skills add https://github.com/enchantednatures/.dotfiles --skill test-driven-development-enchantednatures

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/enchantednatures/.dotfiles/tree/main/.config/opencode/skills/test-driven-development
Command: npx skills add https://github.com/enchantednatures/.dotfiles --skill test-driven-development-enchantednatures

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing tests after code can miss edge cases and lead to unstable software; this skill promotes a test-first approach to lock in expected behavior and prevent regressions.

Core Features & Use Cases

Test-first workflow: Write a failing test, then implement the minimal code to satisfy it, and repeat.
Scope of use: Applies to new features, bug fixes, refactoring, and behavior changes to ensure correct, maintainable software.
Quality discipline: Enforces the cycle of RED-GREEN-REFACTOR and prevents code with no tests.

Quick Start

Draft a small failing test for the desired behavior, then implement the minimal code to make it pass, and repeat the cycle until all tests pass.

Frequently Asked Questions about test-driven-development

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

FAQPage Schema

How does test-driven development prevent software regressions?▼

Test-driven development prevents regressions by enforcing a test-first workflow where you write a failing test before implementing production code. This locks in expected behavior and ensures all features maintain correct behavior during refactoring.

How do I apply the Red-Green-Refactor cycle when fixing bugs?▼

To apply the Red-Green-Refactor cycle for bug fixes, you draft a small failing test that captures the bug, implement the minimal code to make it pass, and then refactor the code as needed to satisfy all tests.

Can I use this test-first workflow for refactoring existing features?▼

Yes, you can use the test-first workflow for refactoring existing features. You write tests to lock in the current expected behavior before changing the code, preventing unstable software during behavior modifications.

What's the best way to start writing code using a test-driven approach?▼

The best way to start is to draft a small failing test for the desired behavior, implement the minimal production code required to make that specific test pass, and repeat the cycle until all tests pass.

Why does writing tests after code lead to missing edge cases?▼

Writing tests after code leads to missing edge cases because production logic is already implemented, making it difficult to accurately capture all expected behaviors and prevent regressions in unstable software.