Meta-tests for resyntax/test failure reporting
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 75/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Quiet
- Domain
- testing
Research direction
Start with test/private/rackunit.rkt and inspect the code handling code-block pretty-printing and failure message rendering. Then review the raise-syntax-error paths in test.rkt and run the relevant checks through rackunit's run-test-case. Done means deliberately failing meta-tests assert the expected failure output and cover the unbound and non-statement identifier paths.
Written by the indexing model from the issue text.
Description
test/private/rackunit.rkt is at 76.8% coverage (69 missed lines), and the misses are exactly the code that runs when a refactoring test fails: the code-block pretty-printing writer and the failure message rendering. The raise-syntax-error paths in test.rkt for unbound or non-statement identifiers are similarly untested. Covering these means meta-tests: deliberately-failing checks run via rackunit's run-test-case with assertions on the failure output.
This is worth more than the coverage points. Reviewers lean on this failure output when reviewing AI-written rule PRs, and right now it's the least-tested part of the test framework itself.
Part of #680.
- Dominant language
- Racket
- Stars
- 70
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from jackfirth/resyntax
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
documentation
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
testing
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
testing
Difficulty 4/5 3-5 days Newbie friendliness 68/100
-
new lint
Difficulty 3/5 1-2 days Newbie friendliness 55/100
All issues in jackfirth/resyntax
Similar issues
-
area:spec bug good first issue ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
low smart-contract Stellar Wave testing
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Web3Novalabs/Nevo#1376 · 3 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 1/5 Under an hour Newbie friendliness 60/100
github/gh-aw-mcpg#13748 ·