Skip to content

case C: a grader for claims that the picker test file is absent - #44

Merged
buzzdan merged 1 commit into
mainfrom
claude/no-absent-test-claim
Oct 18, 2026
Merged

buzzdan merged 1 commit into
mainfrom
claude/no-absent-test-claim

Conversation

@buzzdan

@buzzdan buzzdan commented Oct 14, 2026 •

Copy link
Copy Markdown
Owner

What

A new grader, no-absent-test-claim, for case C in every suite. It fails a report that calls the picker's test file absent, missing or not found. Each suite names its own file: picker.test.ts (ts-react, and its neutral variant), picker_test.go (go), test_picker.py (py).

Why

In the ts-react A/B, a hunter reported picker.test.ts as absent while it existed. The plugin side is buzzdan/ai-coding-rules#91 (merged), with the budget clause in buzzdan/ai-coding-rules#99.

Checks

  • All four graders load with evalcase.LoadGrader, and evalcase.Discover loads all three suites.
  • The pattern matches "picker.test.ts is absent" and "no picker.test.ts". It does not match "picker.test.ts:12 missing a row".
  • Not regraded against the baselines: they keep result.json only, not the report text.

🤖 Generated with Claude Code

A hunter once reported the picker's test file as absent while it existed.
no-absent-test-claim fails a report that says the file is absent, missing or
not found. Each suite names its own file: picker.test.ts (ts-react, and its
neutral variant), picker_test.go (go), test_picker.py (py).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@buzzdan

buzzdan commented Oct 18, 2026

Copy link
Copy Markdown
Owner Author

The plugin side is now buzzdan/ai-coding-rules#91 (merged) and buzzdan/ai-coding-rules#99. #93 is closed as a duplicate.

@buzzdan
buzzdan merged commit 96f1024 into main Oct 18, 2026
3 checks passed
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