Receber por email
← Voltar para o catálogo

test-driven-development

Aplicação estrita do ciclo RED-GREEN-REFACTOR. Testes nunca são ignorados ou adiados, sempre em modo de execução, com evidência obrigatória do código de saída.

1.4kestrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add a5c-ai/babysitter

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/test-driven-development-a5c-ai/svg)](https://www.skillteca.com.br/skills/test-driven-development-a5c-ai)

Skills relacionadas

Ver todas de Desenvolvimento →

Alerta por categoria

Receba novas skills de Desenvolvimento toda segunda

1 email curto, só com as skills novas de Desenvolvimento. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Test-Driven Development

Overview

Enforces the TDD discipline in all CC10X BUILD workflows. The RED-GREEN-REFACTOR cycle is mandatory and cannot be skipped or deferred.

TDD Cycle

  1. RED: Write failing test first. Run with CI=true npm test or --run flag. Exit code MUST be 1.
  2. GREEN: Write minimal code to make test pass. Exit code MUST be 0.
  3. REFACTOR: Clean up implementation while keeping tests green. Exit code MUST remain 0.

Non-Negotiable Rules

  • Always use run mode (CI=true npm test or --run flag)
  • NEVER use watch mode (prevents hanging processes)
  • Use timeout guards (timeout 60s) as backup
  • Record exit codes as evidence at each phase
  • If tests fail 3 consecutive times in GREEN, report failure status
  • Never skip RED phase (failing test must exist before implementation)
  • Never defer tests to "later" -- TDD means tests first

Scope Discipline

  • If implementation requires >3 file changes, flag for scope review
  • Architectural choices require user approval unless pre-approved in plan
  • New dependencies require user approval

When to Use

  • Every feature implementation in BUILD workflow
  • Every bug fix in DEBUG workflow (regression test)

Agents Used

  • component-builder (primary consumer)
  • bug-investigator (regression tests)
Compartilhar X LinkedIn