Fuzz testing
Open
- Dominant language
- C++
- Stars
- 11
- Forks
- 4
- Avg merge
- 16h 39m
- Merged PRs (30d)
- 131
Description
We should stress test out implementation to check that all failures are expected and ideally user-intelligible.
We should explore:
- [ ] Valid and invalid interfaces
- [ ] Conformant and non conformant types
- [ ] violated preconditions
Contributor guide
Research direction
No files or test entry points are named. Start by locating the C++ implementation and existing test harness, then cover the listed valid and invalid interfaces, conformant and non-conformant types, and violated preconditions. Done means the failures are expected and user-intelligible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100