chore(aidd-craft): decide how far craft goes on mutation testing

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

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
1/5
預估耗時
1 小時以內
新手友好度
25/100
Issue 類型
功能
描述清晰度
描述清楚
活躍度
活躍
技術堆疊
typescript
領域
tooling

研究方向

Read the issue’s two options and recommendation, then check Epic #1259 for the success evidence referenced here. The issue is done when one option is chosen and the decision is recorded; the requested opinion from @blafourcade is still pending, so this is not ready for a newcomer to implement.

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

描述

Epic: #1259

Decision needed

The craft rules make killed mutants, not coverage, the measure of test quality. aidd-dev:06-test forbids installing a mutation dependency. How far should aidd-craft go?

Options

  • (a) A rule recommends mutation testing; craft never installs a tool.
  • (b) init proposes the mutation tool matching the stack and installs it only on the user's approval.

Recommendation: (a)

Stack- and tool-agnostic, consistent with aidd-dev, and keeps init free of dependencies.
Trade-off, on quality: killed mutants are the only objective check that the tests are worth something. Under (a), the autonomous TDD mode has no such measure; only the judgment of the validation and review steps remains, which is subjective. (a) trades test quality in autonomous mode for agnosticism, and the Epic's success evidence cannot measure mutation until a tool exists in the project.

@blafourcade: your opinion is wanted on this trade-off specifically.

Done when

One option is chosen and recorded on this issue.

主要語言
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 摘要。