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

未關閉
#1,263 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
45/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
typescript

研究方向

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.

由索引模型根據 Issue 內容生成。

描述

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.
主要語言
TypeScript
星號
481
分支
45
平均合併
1 天 13 小時
30 天內合併 PR
91

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

ai-driven-dev/framework 的其他 Issue

查看 ai-driven-dev/framework 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。