Measure code coverage during fuzzing
Open
Nobody has claimed this yet.
tendril
- Dominant language
- Rust
- Stars
- 2.6k
- Forks
- 288
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 8
Description
Measure the code paths & conditions that occur. Don't stop a fuzzing run until we've hit a quota for each.
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
The issue names no files, fuzzing harness, or tests. Start by locating the repository's fuzzing entry point and how coverage is currently collected, then determine how path and condition quotas should be represented. Done means fuzzing measures both kinds of coverage and does not stop before their quotas are met.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100