Workflow TDD

VérifiéSûr

Principes du développement piloté par les tests : cycle ROUGE-VERT-REFACTOR.

Spar Skills Guide Bot
DeveloppementIntermédiaire
1025/07/2026
Claude CodeCursorWindsurfCopilotCodex
#test-driven-development#red-green-refactor#testing-practices#aaa-pattern#code-quality

Recommandé pour

Notre avis

Ce skill implémente le cycle TDD (Test-Driven Development) : écrire un test qui échoue, coder le minimum pour le passer, puis refactoriser.

Points forts

  • Guide structuré en trois phases claires (ROUGE, VERT, REFACTOR) avec règles précises.
  • Insiste sur l'écriture de tests avant le code, réduisant les bugs et améliorant la conception.
  • Inclut des anti-patrons et des conseils pour l'utilisation avec l'IA (multi-agent).
  • Applique les principes YAGNI et de simplicité maximale.

Limites

  • Nécessite une discipline rigoureuse, difficile à appliquer dans des contextes exploratoires ou d'UI.
  • Peut ralentir le développement initial, surtout pour des fonctionnalités simples.
  • Ne couvre pas les tests de performance ou d'intégration complexes.
Quand l'utiliser

Utilisez ce skill pour développer des fonctionnalités nouvelles, corriger des bugs ou implémenter une logique complexe avec une couverture de test fiable.

Quand l'éviter

Évitez-le pour le prototypage rapide, l'exploration de concepts ou les scripts jetables où la vélocité prime sur la qualité.

Analyse de sécurité

Sûr
Score qualité92/100

The skill is an educational guide on Test-Driven Development principles. It contains no instructions for destructive or exfiltrating actions, and the allowed 'Bash' tool is for legitimate development tasks, not misused in the content.

Aucun point d'attention détecté

Exemples

TDD for a new feature
Guide me through TDD for adding a 'calculate_discount' function: first write a failing test, then minimal code, then refactor.
TDD bug fix
Apply the RED-GREEN-REFACTOR cycle to fix a bug: write a test that reproduces the bug, then fix the code, then refactor.
AAA pattern demo
Show me an example of the Arrange-Act-Assert pattern for testing a function that validates email addresses.

name: tdd-workflow description: Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle. allowed-tools: Read, Write, Edit, Glob, Grep, Bash

TDD Workflow

Write tests first, code second.


1. The TDD Cycle

🔴 RED → Write failing test
    ↓
🟢 GREEN → Write minimal code to pass
    ↓
🔵 REFACTOR → Improve code quality
    ↓
   Repeat...

2. The Three Laws of TDD

  1. Write production code only to make a failing test pass
  2. Write only enough test to demonstrate failure
  3. Write only enough code to make the test pass

3. RED Phase Principles

What to Write

| Focus | Example | |-------|---------| | Behavior | "should add two numbers" | | Edge cases | "should handle empty input" | | Error states | "should throw for invalid data" |

RED Phase Rules

  • Test must fail first
  • Test name describes expected behavior
  • One assertion per test (ideally)

4. GREEN Phase Principles

Minimum Code

| Principle | Meaning | |-----------|---------| | YAGNI | You Aren't Gonna Need It | | Simplest thing | Write the minimum to pass | | No optimization | Just make it work |

GREEN Phase Rules

  • Don't write unneeded code
  • Don't optimize yet
  • Pass the test, nothing more

5. REFACTOR Phase Principles

What to Improve

| Area | Action | |------|--------| | Duplication | Extract common code | | Naming | Make intent clear | | Structure | Improve organization | | Complexity | Simplify logic |

REFACTOR Rules

  • All tests must stay green
  • Small incremental changes
  • Commit after each refactor

6. AAA Pattern

Every test follows:

| Step | Purpose | |------|---------| | Arrange | Set up test data | | Act | Execute code under test | | Assert | Verify expected outcome |


7. When to Use TDD

| Scenario | TDD Value | |----------|-----------| | New feature | High | | Bug fix | High (write test first) | | Complex logic | High | | Exploratory | Low (spike, then TDD) | | UI layout | Low |


8. Test Prioritization

| Priority | Test Type | |----------|-----------| | 1 | Happy path | | 2 | Error cases | | 3 | Edge cases | | 4 | Performance |


9. Anti-Patterns

| ❌ Don't | ✅ Do | |----------|-------| | Skip the RED phase | Watch test fail first | | Write tests after | Write tests before | | Over-engineer initial | Keep it simple | | Multiple asserts | One behavior per test | | Test implementation | Test behavior |


10. AI-Augmented TDD

Multi-Agent Pattern

| Agent | Role | |-------|------| | Agent A | Write failing tests (RED) | | Agent B | Implement to pass (GREEN) | | Agent C | Optimize (REFACTOR) |


Remember: The test is the specification. If you can't write a test, you don't understand the requirement.

Skills similaires