Skip to content

test: harden coverage of numeric/range helpers past the 100% knife-edge - #551

Merged
tannevaled merged 1 commit into
mainfrom
chore/coverage-harden
Sep 3, 2026
Merged

tannevaled merged 1 commit into
mainfrom
chore/coverage-harden

Conversation

@tannevaled

Copy link
Copy Markdown
Contributor

The merged coverage gate sat on the ~99.94% rounding boundary — complexEqual, rationalEqual, rangeInts, rangeSize, rangeElems had branches the operator/opcode paths never hit, so any PR adding code could tip the -race POSIX total below 100.0% even with its own additions fully covered (this repeatedly failed #549 despite its functions all being 100%). This drives those five helpers through every branch via a whitebox internal test + MRI-checked eval cases. Merged total is now 100.0% with margin, so the strict gate stops flaking.

🤖 Generated with Claude Code

The merged coverage gate sat on the 99.94% rounding boundary: complexEqual
(80%), rationalEqual (83%), rangeInts (80%), rangeSize (78%) and rangeElems
(93%) had branches the operator/opcode paths never exercised, so a PR adding
any code could tip the -race total below 100.0% on the POSIX lanes even with
its own additions fully covered. Drive those five helpers through every branch
(Complex/Rational == against Complex/Rational/Float/real/non-numeric; Range
size/elems across inclusive, exclusive, empty, String and the non-integer
TypeError) via a whitebox internal test plus MRI-checked eval cases. The merged
total is now 100.0% with margin.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@tannevaled
tannevaled merged commit 5a58a17 into main Sep 3, 2026
7 checks passed
@tannevaled
tannevaled deleted the chore/coverage-harden branch September 3, 2026 17:19
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