skills.rest
reez455G
reez455GCOMMUNITY
Explore all skills by this author →
GitHub

test-driven-development

Guide developers through the test-driven development cycle with RED, GREEN, REFACTOR.

Updated Jul 7, 2026
Search Tags:#TDD#unit testing#test-driven development#software testing#bug fixes
One-click install
npx skills add https://github.com/reez455G/my-ai-agents --skill test-driven-development-reez455g
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/reez455G/my-ai-agents/tree/main/.omp/skills/test-driven-development
Command: npx skills add https://github.com/reez455G/my-ai-agents --skill test-driven-development-reez455g

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill promotes and facilitates test-driven development (TDD), ensuring code reliability and maintainability by prioritizing testing throughout the development process.

Core Features & Use Cases

  • Test-Driven Development Workflow: Guides through the TDD cycle (RED, GREEN, REFACTOR) for writing tests before coding.
  • Bug Fixes with Tests: Encourages the Prove-It Pattern, where a test is written to reproduce a bug before attempting a fix.
  • Test Pyramid: Suggests a structured approach to testing, with a focus on small, fast unit tests at the base, moving up to larger, more complex end-to-end tests.

Quick Start

To start implementing a new feature using TDD, begin by writing a test for the expected behavior and watch it fail.

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 test-driven development for a new feature?▼

Test-driven development begins by writing a unit test for the expected behavior and watching it fail. You then write code to pass the test, and refactor while ensuring the tests stay green.

What is the best way to fix bugs using test-driven development?▼

Bug fixes in test-driven development use the Prove-It Pattern: write a unit test that reproduces the bug before attempting a fix. This ensures the software testing process validates the actual defect.

How does the TDD cycle work when writing unit tests?▼

The TDD cycle consists of three phases: RED, where a test is written and fails; GREEN, where code is written to pass the test; and REFACTOR, where the code is improved while maintaining passing tests.

Do I need to know unit testing frameworks to use test-driven development?▼

Yes, test-driven development requires existing knowledge of unit testing and test frameworks. The Skill guides the TDD workflow but expects you to understand how to implement software testing.

What is the Test Pyramid approach in software testing?▼

The Test Pyramid suggests a structured approach to software testing, prioritizing small, fast unit tests as the base and moving up to larger, more complex end-to-end tests for comprehensive coverage.

When should I not use test-driven development?▼

Test-driven development is designed for logic implementation and bug fixes where behavior can be explicitly defined by unit tests. It may not suit exploratory coding or UI design where testing frameworks cannot easily capture expected behavior.

Related Skills

Explore More Software Engineering Skills→
rundeckrundeck
6.3k

create-test

Automate backend test creation for Rundeck applications using Spock and Testcontainers.

Official
Advanced
SeaBrad72SeaBrad72
1

tdd

Enforce a red-green-refactor cycle requiring failing tests before production code.

Community
Advanced
DaniloUnicamDaniloUnicam

test-coverage-improver

Analyzes software test coverage and suggests targeted tests for improvement.

Community
Intermediate
salvo-rssalvo-rs
20

salvo-testing

Validate Salvo handlers, middleware, and routing with TestClient.

Official
Intermediate