Introduce fuzzer tests
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1k
- Forks
- 423
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 24
Description
Enhancement
We have some randomized tests, for example, https://github.com/pingcap/tiflash/pull/5150.
In these randomized tests, the selection of operation is purely random. As an improvement, we can use fuzzers to drive these tests. Fuzzers can automatically choose input workloads based on the observation of the execution path coverage, which is much more efficient to cover different kind of branches.
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 randomized tests described in pull request 5150 and how they select operations. Investigate how a fuzzer could drive those tests using execution-path coverage. Done means introducing fuzzer tests that cover workloads more efficiently than purely random operation selection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100