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

Đang mở
#222 0 bình luận 0 reaction 0 người được giao Xem trên GitHub

Maintainer thường phản hồi trong vòng 1 ngày

Chưa có ai nhận issue này.

Đánh giá

Độ khó
4/5
Thời gian dự kiến
Hơn một tuần
Mức phù hợp với người mới
15/100
Loại issue
Tính năng
Độ rõ ràng
Khá rõ ràng
Mức độ hoạt động
Sôi nổi
Công nghệ
github-actions, go
Lĩnh vực
testing

Hướng nghiên cứu

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.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.

Mô tả

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

Ngôn ngữ chính
Go
Star
0
Fork
0
Merge trung bình
7 giờ 42 phút
Pull request đã merge (30 ngày)
111

Chuẩn bị môi trường

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của seanb4t/codegraph-go

Tất cả issue của seanb4t/codegraph-go

Issue tương tự

Thêm issue về Go

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.