chore(test): trial a mutation testing tool (gremlins or go-mutesting) after the property tests land
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
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
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
- Wait for the sync-equals-reindex property and the
keyencfuzz target from #221. - Run each candidate once over
internal/indexerandinternal/graphstore. Record killed, lived, not covered, not viable, and minutes per run. - 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. - Read every
LIVEDline. 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. Forgremlins, as a GitHub release withmise.lockchecksums. Forgo-mutesting, resolve the Go 1.27 requirement first. - Run it on changed lines only, through
paths-filterfrom #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
- Lenguaje dominante
- Go
- Estrellas
- 0
- Forks
- 0
- Merge medio
- 7 h 42 min
- PR fusionados (30 d)
- 111
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de seanb4t/codegraph-go
-
chore needs-triage
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
seanb4t/codegraph-go#380 ·
Los mantenedores suelen responder en 1 día
-
chore needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
seanb4t/codegraph-go#379 ·
Los mantenedores suelen responder en 1 día
-
area:query chore needs-triage spec-needed
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
seanb4t/codegraph-go#377 ·
Los mantenedores suelen responder en 1 día
-
chore needs-triage
Dificultad 1/5 1-3 horas Aptitud para principiantes 84/100
seanb4t/codegraph-go#362 ·
Los mantenedores suelen responder en 1 día
-
area:query bug needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
seanb4t/codegraph-go#355 ·
Los mantenedores suelen responder en 1 día
Todos los issues de seanb4t/codegraph-go
Issues similares
-
Add iterate GmbH domains to a dedicated list and include it in company and developer categoriesAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
v2fly/domain-list-community#4307 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
Los mantenedores suelen responder en 1 día
-
notify: voice_queue rows are deleted only at startup, so a hub that stays up grows it without boundAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
mattabate/life-distributable#232 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 86/100
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 83/100
Los mantenedores suelen responder en 1 día