Wrap-Up: An Input Coverage Playbook
This post is part of the Input Coverage > Code Coverage series.
- Start with property tests. Prove the obvious.
- Add libFuzzer on raw bytes. Hunt the non-obvious.
- Add AFL++ for stdin and CLI and process-level issues.
- One entry point. One Makefile. Short runs by default.
- Turn crashes into tests. Keep them forever.
- Cap resource use. Bound lengths and counts.
- Mock I/O. Keep the hot path fast.
- Keep corpora small and clean.
- Only increase complexity when it pays off.
Less ceremony. More input coverage. Fewer surprises.