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 摘要。