feat: add config to target/exclude func sig. by contract #400
Conversation
This file contains 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
0xalpharush
force-pushed
the
feat/target-and-exclude-signatures
branch
from
e3d43e9
to
5a66fa2
Compare
anishnaik
reviewed
Jul 18, 2024
anishnaik
reviewed
Jul 18, 2024
anishnaik
reviewed
Jul 18, 2024
anishnaik
reviewed
Jul 18, 2024
anishnaik
reviewed
Jul 18, 2024
anishnaik
approved these changes
Jul 18, 2024
0xalpharush
added a commit
that referenced
this pull request
Jul 25, 2024
This reverts commit 9a2d0d9.
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.
Closes #248 and replaces #275
I refactored the detection of assertion, property, and optimization tests to be split into groups upfront rather than iterating over all methods and determining if they should be tested constantly in the main fuzzing loop. This grouping occurs after filtering the available contract methods against the list of target function signatures and excluded function signatures (mutually exclusive). Filtering function signatures does not disable calling property and optimization tests which will always be tested unless those testing modes are disabled.