skills.rest
alissonpef
alissonpefCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

test-driven-development

Write a failing test before implementing code changes.

Updated Apr 21, 2026
Search Tags:#testing#refactoring#test-driven development#regression prevention#browser testing#bug fixes
One-click install
npx skills add https://github.com/alissonpef/copilot-agent-skills --skill test-driven-development-alissonpef
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/alissonpef/copilot-agent-skills/tree/main/.github/skills/test-driven-development
Command: npx skills add https://github.com/alissonpef/copilot-agent-skills --skill test-driven-development-alissonpef

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you build and change software with confidence by requiring tests before code, making bugs visible early and preventing regressions from slipping into production.

Core Features & Use Cases

  • Test-First Workflow: Write a failing test, implement the smallest fix, then refactor while keeping the suite green.
  • Bug Reproduction: Turn bug reports into proof by capturing the defect in a test before attempting a fix.
  • Behavior-Focused Validation: Verify outcomes instead of internal implementation details so tests stay useful during refactors.
  • Browser and UI Support: Combine unit tests with runtime checks for browser-based changes when visual or interaction verification is needed.

Quick Start

Ask the assistant to write a failing test for your change first, then implement the smallest code change that makes it pass.

Frequently Asked Questions about test-driven-development

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

FAQPage Schema
What is test-driven development and how does it prevent regressions?▼

Test-driven development is a workflow where you write a failing test before implementation, making bugs visible early and preventing regressions from slipping into production.

How do I write a reproduction test for a bug fix?▼

To write a reproduction test for a bug fix, capture the defect in a failing test that proves the incorrect behavior before attempting any code fix. This ensures the bug is accurately reproduced.

How do I refactor code without breaking existing behavior tests?▼

To refactor code without breaking behavior tests, verify outcomes using behavior-focused assertions rather than internal implementation details. This keeps tests useful and green during refactoring.

Can I use test-driven development for browser and UI testing workflows?▼

Yes, test-driven development supports browser and UI testing workflows by combining unit tests with runtime checks for browser-based changes when visual or interaction verification is needed.

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

The red-green-refactor cycle in test-first development requires writing a failing test, implementing the smallest code fix to make it pass, then refactoring while keeping the test suite green.

Does behavior-focused validation require checking internal implementation details?▼

No, behavior-focused validation verifies outcomes instead of internal implementation details. This approach ensures tests remain useful and accurate during subsequent code refactoring.

Related Skills

Explore More Software Engineering Skills→
Ced3-hanCed3-han

tdd-workflow

Enforce a Test-Driven Development workflow with unit, integration, and end-to-end tests.

Community
Intermediate
Marshall-HallenbeckMarshall-Hallenbeck
5

fix-tests

Diagnose and repair failing test suites across multiple language ecosystems.

Community
Advanced
sscciossccio

tdd

Enforce Red-Green-Refactor sequencing with one failing test per feature.

Community
Basic
mscipiomscipio

atdd

Generates executable test specifications for workflows using GanttProject's Umlet integration.

Community
Intermediate