RoaringBitmap / RoaringBitmap/roaring
Fuzz testing
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.9k
- Forks
- 262
- Avg merge
- 2h 34m
- Merged PRs (30d)
- 8
Description
One of the most primary types of test we use to ensure that the library works well is unit testing.
We can't rely on only these tests, as there is a big probability of human errors.
Fuzz testing is a good candidate which could help us to make the package more tolerant to randomized/invalid data inputs.
There are some platforms that offer continuous fuzzing
Contributor guide
No contributing guide indexed for this repository
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 repository's existing unit tests, then read the linked go-fuzz documentation and continuous-fuzzing platforms. Define which randomized or invalid inputs should be exercised and how fuzzing would run for this Go library; the work is done when an agreed fuzz-testing approach is implemented and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100