chore(test): trial a mutation testing tool (gremlins or go-mutesting) after the property tests land

Abierto
#222 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
4/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
15/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github-actions, go
Área
testing

Línea de trabajo

This is blocked by #221, so wait for its property and fuzz tests to merge before starting. Once they have, run each candidate tool over internal/indexer and internal/graphstore, then over the changed lines of five real PRs, and classify every LIVED mutant. Done means the counts and the adoption decision are recorded in this issue, with mise.toml and mise.lock updated only if a tool is adopted.

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

Descripción

area:ci chore priority:low
What kind of chore?

Test infrastructure

What needs doing?

After the property and fuzz tests from #221 land, trial a mutation testing tool. Adopt it only when the trial meets the entry test below. #221 deletes the repo's own scripts/mutation_check.py, its unit tests, task mutation-check and the mutation-check skill. Nothing replaces them until this trial decides.

Candidates

Both are active. Facts as of 2026-10-31:

go-gremlins/gremlins avito-tech/go-mutesting
latest release v0.6.0, 2025-12-06 v2.3.1, 2025-12-26
install release tarballs with a checksums file, so mise.lock records them no release assets, go install only
Go required 1.25 1.27. The repo pins 1.26.10 with GOTOOLCHAIN=local, so this needs a toolchain decision first
scope to what changed diff: mutates only changed lines, and coverage guidance skips uncovered lines targets are files or packages, no line-level diff
how tests run on a copy, the tree is untouched replaces the original file in place, then restores it
CI gate threshold.efficacy and threshold.mutant-coverage a printed mutation score, parsed by the caller
mutators 11, 5 on by default. No statement or branch removal a larger set: branch, statement removal, loop break, numbers, expression
suppression exclude-files inline mutator-disable-next-line comments in product source
license Apache-2.0 MIT

Neither is assumed. The trial runs both over the same packages and the same PRs.

Entry test
  1. Wait for the sync-equals-reindex property and the keyenc fuzz target from #221.
  2. Run each candidate once over internal/indexer and internal/graphstore. Record killed, lived, not covered, not viable, and minutes per run.
  3. Run each candidate over the changed lines of the next five real PRs. For go-mutesting, pass the changed files as targets. Record the same counts and minutes.
  4. Read every LIVED line. Mark each one as one of three kinds. A real gap means a reviewer agrees a test is missing. Noise means an equivalent mutant. A generator gap means a property does not reach the line.

To adopt a tool as a CI gate, both of these must hold:

  • At least one surviving mutant was a real gap or a generator gap that led to a stronger test.
  • The per-PR cost on changed lines stayed under a few minutes.

If neither tool meets that, the outcome is still useful. Record the counts in this issue, close it, and leave the tool as something anyone can run locally.

If adopted
  • Pin the tool in mise.toml. For gremlins, as a GitHub release with mise.lock checksums. For go-mutesting, resolve the Go 1.27 requirement first.
  • Run it on changed lines only, through paths-filter from #221, never over the whole module on every push.
  • The gate asserts that it mutated at least one line (rule 84d1gfpywd). A run that mutates nothing fails.
  • Rewrite the fix PR template's "I watched it fail before the fix" proof to accept the tool's report instead of pasted output.
  • Put no tool-specific disable comments in product source.
Why now?

Not now. This issue exists so the deletion in #221 has a named successor and an entry test, instead of a silent gap. When part 3 of #221 (property and fuzz tests) merges, this trial starts.

Does this touch anything load-bearing?
  • The release pipeline (release.yml, .goreleaser.yaml, signing)
  • The upgrade identity (internal/upgrade/verify.go)
  • The perf baseline (tools/bench/baseline.json)
  • The graph schema / meta-key layout
  • None of these
Before submitting
  • I searched existing issues and this is not a duplicate

Blocked by #221. Related: #176 and #182 (the skill this replaces).

🤖 Generated with Claude Code

https://claude.ai/code/session_0167DcypPuyLUHrwdrVKYYG8

Lenguaje dominante
Go
Estrellas
0
Forks
0
Merge medio
7 h 42 min
PR fusionados (30 d)
111

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 seanb4t/codegraph-go

Todos los issues de seanb4t/codegraph-go

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.