feat(aidd-craft): drive a behavior test-first, one test at a time

Abierto
#1,263 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript

Línea de trabajo

The issue defines the behavior for the tdd workflow, but does not name implementation files or tests. Start by locating the tdd entry point and its existing tests, then trace how it receives behavior criteria and controls test and code changes. Done means the workflow follows each acceptance criterion, including handing back when criteria are missing or too technical.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Epic: #1259

Story

As a developer
I want tdd to show the ordered test list before the first test, then advance one test at a time, asking before going red and before going green
So that the design emerges under my control

Acceptance

  • Input is a behavior with verifiable acceptance criteria, from a story, a plan phase, a spec or a defect; without criteria, tdd hands back.
  • Criteria must describe business behavior: criteria naming HTTP, SQL, a UI or another technical detail are handed back. Tests target the use case entry point, not the delivery mechanism.
  • The test list goes from the most specific case to the most general, each test named after its final rule.
  • One failing test at a time; a compile or import error does not count as red.
  • Green writes only what the current test requires, clean on the first pass; refactoring is optional and deep only.
  • A red test leads to a code change, never to editing the test until it passes.
Lenguaje dominante
TypeScript
Estrellas
481
Forks
45
Merge medio
1 d 13 h
PR fusionados (30 d)
91

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de ai-driven-dev/framework

Todos los issues de ai-driven-dev/framework

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.