skills.rest
guccang
guccangCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

test-driven-development

Create failing tests before implementing minimal production code.

3|1|Updated Apr 19, 2024
Search Tags:#testing#tdd#quality assurance#software development#red-green-refactor#regression testing
One-click install
npx skills add https://github.com/guccang/blogclaw --skill test-driven-development-guccang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/guccang/blogclaw/tree/main/cmd/hermes-agent/vendor/hermes_runtime/skills/software-development/test-driven-development
Command: npx skills add https://github.com/guccang/blogclaw --skill test-driven-development-guccang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents unreliable software changes by enforcing a disciplined test-first workflow that catches defects early and keeps implementation aligned with expected behavior.

Core Features & Use Cases

  • RED-GREEN-REFACTOR Workflow: Guides developers to write failing tests first, implement minimal solutions, and refactor safely while maintaining passing tests.
  • Test Quality Practices: Encourages behavior-focused tests, regression coverage, and avoiding implementation-dependent testing patterns.
  • Use Case: Help a developer implement a new feature or fix a bug by creating a failing test, writing the smallest passing implementation, and validating the complete test suite.

Quick Start

Use the test-driven-development skill to implement the requested feature by writing a failing test first and following the RED-GREEN-REFACTOR cycle.

Frequently Asked Questions about test-driven-development

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

FAQPage Schema
How do I implement test-driven development for a new feature?▼

Test-driven development for bug fixes involves creating a failing test that reproduces the defect, writing the smallest code implementation to make it pass, and running regression tests to verify the fix.

What is the RED-GREEN-REFACTOR cycle in software development?▼

The RED-GREEN-REFACTOR cycle in software development is a test-first practice where you write a failing test, implement the minimal code to pass it, and then refactor the code while keeping the tests green.

How do I use test-first development to fix a bug?▼

Using test-first development to fix a bug requires creating a failing test that reproduces the defect, writing the smallest code implementation to make it pass, and validating the complete regression test suite.

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

Test-driven development works for refactoring existing code by guiding you to maintain passing tests while safely changing the implementation, ensuring behavior-focused quality standards and reliable automated verification.

When should I not use test-driven development for software changes?▼

You should not use test-driven development for software changes that do not require reliable automated verification or behavior-focused quality standards, as the workflow strictly enforces test-first validation for all implementation changes.

Related Skills

Explore More Software Engineering Skills→
vneseyoungstervneseyoungster
27

test-driven-development

Write failing tests before implementing minimal code to pass them.

Community
Advanced
Sheldon-92Sheldon-92
3

Testing

Execute test suites and report failures with coverage metrics.

Community
Intermediate
theinternetitheinterneti

gitnexus-refactoring

Rename, extract, and split code modules within a Git repository.

Community
Advanced
thkim2015thkim2015

moai-workflow-tdd

Guide developers through the RED-GREEN-REFACTOR cycle for new features.

Community
Advanced