chore(test): trial a mutation testing tool (gremlins or go-mutesting) after the property tests land
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 15/100
調査の方向性
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.
索引モデルが issue の本文から書いたものです。
説明
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
- 主要言語
- Go
- スター
- 0
- フォーク
- 0
- 平均マージ
- 7時間 42分
- マージ済み PR(30日)
- 111
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
seanb4t/codegraph-go のほかの issue
-
chore needs-triage
難易度 1/5 1時間未満 初心者へのやさしさ 88/100
seanb4t/codegraph-go#380 ·
メンテナーはふだん 1 日以内に返信
-
chore needs-triage
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
seanb4t/codegraph-go#379 ·
メンテナーはふだん 1 日以内に返信
-
area:query chore needs-triage spec-needed
難易度 2/5 1〜3時間 初心者へのやさしさ 74/100
seanb4t/codegraph-go#377 ·
メンテナーはふだん 1 日以内に返信
-
chore needs-triage
難易度 1/5 1〜3時間 初心者へのやさしさ 84/100
seanb4t/codegraph-go#362 ·
メンテナーはふだん 1 日以内に返信
-
area:query bug needs-triage
難易度 2/5 1〜3時間 初心者へのやさしさ 80/100
seanb4t/codegraph-go#355 ·
メンテナーはふだん 1 日以内に返信
seanb4t/codegraph-go の issue をすべて見る
似ている issue
-
Add iterate GmbH domains to a dedicated list and include it in company and developer categoriesオープン
難易度 2/5 1〜3時間 初心者へのやさしさ 66/100
v2fly/domain-list-community#4307 ·
メンテナーはふだん 1 日以内に返信
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 86/100
メンテナーはふだん 1 日以内に返信
-
notify: voice_queue rows are deleted only at startup, so a hub that stays up grows it without boundオープン
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
mattabate/life-distributable#232 ·
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 86/100
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1〜3時間 初心者へのやさしさ 83/100
メンテナーはふだん 1 日以内に返信