Repository navigation
Standing fuzz suite and fuzzing log - #42
Merged
Merged
Conversation
- Sources/MicControl.Tests/Fuzz: the three fuzzing rounds' harnesses as opt-in tests (MICCONTROL_FUZZ=1), a new seed each run printed with any failure, MICCONTROL_FUZZ_SEED to repeat and MICCONTROL_FUZZ_SCALE for more cases - tools/FuzzWav.cs: damaged WAVs through the playback decoder, and Avalonia keys with no virtual key - tools/Fuzz.ps1 runs both after a build - docs/fuzzing-report.md: the log of rounds (what each covered, up to which commit, what to try next), read first by every new round
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Requested by Matt · project thread
Before: the three fuzzing rounds' harnesses lived outside the repo, and nothing could re-run them after a new build.
After:
powershell -ExecutionPolicy Bypass -File tools\Fuzz.ps1re-runs them with a new random seed each time (-Scale 5for more cases,-Seed Nto repeat a failure).docs/fuzzing-report.mdis the running log that each new round reads first.How:
Sources/MicControl.Tests/Fuzz/holds 16 opt-in tests, skipped unlessMICCONTROL_FUZZ=1, so normal test runs and CI are unchanged. They cover settings JSON, MicSwitch configs, hotkey text, SSH signatures, the update feed, image headers, command lines, the autostart takeover, huge settings files and the hotkey state machine.FuzzRunmixes the seed, scales the cases and prints the seed with any failure.tools/FuzzWav.csis a file-based app that references the Windows project, because the WAV decoder lives there. It also checks that every key Avalonia can report has a virtual key.Generated by Claude Code