Revise invariant testing documentation#1747
Draft
0xalpharush wants to merge 1 commit intofoundry-rs:masterfrom
Draft
Revise invariant testing documentation#17470xalpharush wants to merge 1 commit intofoundry-rs:masterfrom
0xalpharush wants to merge 1 commit intofoundry-rs:masterfrom
Conversation
Updated section headers and removed function call probability distribution details.
0xalpharush
requested review from
0xrusowsky,
DaniPopes,
grandizzy,
klkvr,
mattsse,
onbjerg and
zerosnacks
as code owners
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
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 function call probability distribution is not accurate when mutational fuzzing is used.
I removed "Type-aware value generation" because all of the generation is aware of the ABI signature and the comment calls that into question.
As an aside, the "Storage Aware Fuzz Inputs" doesn't really track with describing what invariant/optimization mode is and probably should live in some advanced configuration section (alongside other features like collecting values from the AST, logs/events, stack are not discussed.