Add a fuzzer for testing randomized operations #4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The fuzzer creates a random sequence of operations and tries them against a JetKV store. If an inconsistency or panic is detected, the sequence is tried to be minimized into a minimal reproducible example. The fuzzer also outputs a seed, which can be used to create the same sequence of operations again. Currently only targets the file backend, mostly because it contained more logic. With some changes, the fuzzer could also target the memory backend. No windows support because `fork()` is used, but it shouldn't be a big change to use `ChildProcess` instead.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The fuzzer creates a random sequence of operations and tries them against a JetKV store. If an inconsistency or panic is detected, the sequence is tried to be minimized into a minimal reproducible example. The fuzzer also outputs a seed, which can be used to create the same sequence of operations again.
Currently only targets the file backend, mostly because it contained more logic. With some changes, the fuzzer could also target the memory backend.
No windows support because
fork()is used, but it shouldn't be a big change to useChildProcessinstead.It also adds a dependency to zig-arg unconditionally. This can perhaps made more cleverly (by someone who actually knows Zig) into a development dependency or some feature or something.