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

Aberta
#1,265 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
1/5
Tempo estimado
Menos de uma hora
Facilidade para iniciantes
25/100
Tipo de issue
Funcionalidade
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
typescript
Domínio
tooling

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
TypeScript
Estrelas
481
Forks
45
Merge médio
1d 13h
PRs com merge (30d)
91

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de ai-driven-dev/framework

Todas as issues de ai-driven-dev/framework

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.