Add fuzz tests for Reader
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 11
- Forks
- 6
- Avg merge
- 55m
- Merged PRs (30d)
- 1
Description
- Generate fuzz tests
- Run fuzzing locally and fix bugs
- Add github action to run fuzzing for some reasonable duration during PR checks
- If possible get help from OSS Fuzz to run fuzzing continuously
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.
Research direction
Start by reviewing the generated Reader fuzz tests and how fuzzing is currently run locally. Then inspect the repository's GitHub Actions setup and define a reasonable PR-check duration; done means fuzzing runs during pull-request checks. Investigate whether continuous OSS-Fuzz support is feasible as a separate follow-up.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, java
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100