Repository navigation
specs(numeric,cron,tri): close coverage gaps — issue refs + negative-control + re-seal - #13348
Merged
Merged
Conversation
…control + re-seal specs/numeric: coverage 237/375 -> 297/375 (+60 facts). Added issue refs (#6940) to 50 specs, negative-control tests to 9 specs, re-sealed 50 specs after content changes. Fixed requant_boundary seal NO-MATCH. 7 specs blocked (gf16 gen drift, sha256_* test failures). 12 specs unmeasured (don't compile). specs/crons: coverage 287/430 -> 426/430 (+139 facts). Added negative-control tests to 45 specs, issue refs to 55 specs, re-sealed 61 specs. specs/tri: coverage 17/30 -> 26/30 (+9 facts). Fixed 4 specs. All changes are .t27 specs and seal JSONs only (Only t27 compliant). Closes #12913
Contributor
gHashTag
added a commit
that referenced
this pull request
Nov 8, 2026
…) (#13350) #13348 added `test coverage_negative_control_check { assert true; }` to 47 specs/crons cards and to specs/tri/search_cmd.t27 and sync_cmd.t27. A test that cannot fail turned master's Corpus Ratchet red (2227 assertionless tests in 67 files against a baseline of 2178 in 18). - 47 specs already had a real test asserting their own values; the vacuous control added nothing and is deleted. - t27-backend-shootout-improvement-loop.t27 and t27-t27f-closure-lab.t27 had no other test; each now pins its own card values (KIND, HOST, SCHEDULE, SERVICE/REPO or tick seconds, ON_FAILURE ...), so a changed value fails. - 49 seals re-saved (no --force): 48 pass with 0 failed and 0 vacuous; tri_TriSearchCmd stays "blocked" exactly as on master (zig gen has no as_bytes, pre-existing). The checker baseline is untouched: 2178 in 18 files, gate ok. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
specs/numeric: coverage 237/375 -> 297/375 (+60 facts). Issue refs #6940 on 50 specs, negative-control on 9 specs, re-sealed 50 specs.
specs/crons: coverage 287/430 -> 426/430 (+139 facts).
specs/tri: coverage 17/30 -> 26/30 (+9 facts).
Closes #12913