skills.rest
harishgovardhandamodar
harishgovardhandamodarCOMMUNITY
Explore all skills by this author →
GitHub

test-driven-development

Apply test-driven development through failing tests and red-green-refactor cycles.

Updated Apr 8, 2026
Search Tags:#testing#red-green-refactor#software-quality#unit-tests#test-driven-development#bug-fix
One-click install
npx skills add https://github.com/harishgovardhandamodar/adversarialStudy --skill test-driven-development-harishgovardhandamodar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/harishgovardhandamodar/adversarialStudy/tree/main/Distributionally-Adversarial-Attack/.agents/skills/test-driven-development
Command: npx skills add https://github.com/harishgovardhandamodar/adversarialStudy --skill test-driven-development-harishgovardhandamodar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Test-driven development (TDD) helps teams translate requirements into tests first, preventing ambiguous specs and guiding implementation with concrete criteria.

Core Features & Use Cases

  • Reproduce bugs with tests before fixes to ensure regressions are caught.
  • Follow the red-green-refactor cycle to drive incremental, clean code.
  • Leverage patterns like Arrange-Act-Assert and focus on descriptive test names to improve confidence and maintainability.
  • Use a robust test pyramid (unit, integration, end-to-end) to balance speed and coverage.
  • Include best practices for browser testing with runtime verification and guidelines for using subagents for reproducible tests.

Quick Start

Begin by writing a failing test for the desired behavior, then implement the minimal code to make it pass, and finally refactor for clarity and maintainability.

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 guide software implementation?▼

Test-driven development guides implementation by writing failing tests first, ensuring requirements are concrete. It uses the red-green-refactor cycle to incrementally build clean code and prevent ambiguous specifications.

How do I use unit tests to reproduce a bug before fixing it?▼

You reproduce a bug by writing a failing unit test that captures the exact regression scenario. This validates the defect before applying the fix, ensuring the test passes afterward and guards against future regressions.

What is the red-green-refactor cycle in test-driven development?▼

The red-green-refactor cycle begins by writing a failing test for desired behavior, implementing minimal code to pass the test, and refactoring for clarity. This drives incremental, clean code while maintaining a reliable test pyramid.

Does test-driven development work across different programming languages?▼

Yes, test-driven development applies to coding tasks across languages. It emphasizes language-agnostic patterns like Arrange-Act-Assert and DAMP over DRY to improve test maintainability and confidence regardless of the platform.

How do I structure a reliable test pyramid for new software logic?▼

Structure a reliable test pyramid by balancing unit, integration, and end-to-end tests. This validates new logic across speed and coverage levels, using descriptive test names and patterns like Prove-It to guard against regressions.

Related Skills

Explore More Software Engineering Skills→
AvatarGanymedeAvatarGanymede

tdd

Automate Test-Driven Development cycles with failing tests before production code.

Community
Intermediate
DiologIRDiologIR

acceptance-e2e

Automate end-to-end UI tests for web applications using Playwright.

Official
Advanced
IntelliTectIntelliTect

apply-testing-patterns

Automates enterprise-grade unit testing patterns for C# projects.

Official
Advanced
pbdeuchlerpbdeuchler
13

writing-good-tests

Guide unit and integration tests toward behavior-focused, maintainable patterns.

Community
Advanced