Skip to content

docs(testing): explain reading Sonar/PIT as data — coverage and duplication triage#141

Merged
dfa1 merged 1 commit into
mainfrom
docs/testing-signal-triage
Jun 23, 2026
Merged

docs(testing): explain reading Sonar/PIT as data — coverage and duplication triage#141
dfa1 merged 1 commit into
mainfrom
docs/testing-signal-triage

Conversation

@dfa1

@dfa1 dfa1 commented Jun 23, 2026

Copy link
Copy Markdown
Owner

What

Adds a section to docs/testing.md capturing the interpretation framework we used while clearing the Sonar findings on main:

  • An uncovered line is one of three things — missing test, dead code, or defensive-by-contract — and coverage alone cannot tell them apart, but mutation testing can. Explains why PIT is scoped to the bounds/parse classes.
  • Duplication can be real or deliberate — usually factor it out (e.g. the BitpackedEncodingDecoder per-row schedule), but sometimes it is the price of the hot-loop vectorisation rule and the invariant wins.

Pure docs; no code change.

🤖 Generated with Claude Code

…cation triage

Document the interpretation framework discussed while clearing the Sonar
findings: an uncovered line is one of missing-test / dead-code /
defensive-by-contract, coverage cannot tell them apart but mutation testing
can, and flagged duplication is usually real but sometimes the deliberate
price of the hot-loop vectorisation rule (BitpackedEncodingDecoder).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@dfa1 dfa1 merged commit 8999661 into main Jun 23, 2026
6 checks passed
@dfa1 dfa1 deleted the docs/testing-signal-triage branch June 23, 2026 06:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant