Supplement generated tests with a fuzzing framework
Open
Nobody has claimed this yet.
build system
code quality
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 226
- Avg merge
- 10h 41m
- Merged PRs (30d)
- 40
Description
- The test generating code is broken, and hard to maintain, see #89 and #65.
- The automatic tests are massive, resulting in painful renames.
- This strategy is extremely hard to apply to alternative layout strategies (#28).
- These generated tests aren't even complete, and have failed to catch multiple deviations from the spec.
These should be supplemented with a fuzz testing or property-based testing framework.
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-test code and the related issues #89 and #65, then examine how the current strategy applies to alternative layout strategies discussed in #28. Define the fuzzing or property-based testing scope and framework before implementation; done means the new tests supplement the generated tests and cover deviations the current suite misses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100