-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add config to abort on first fail when performing fuzzing #3662
Comments
You can run |
Hey, what I meant is, not related to test selection. Say I'm using |
If you run a single test and run number 34 of that test fails, the test does fail immediately and no other "normal" fuzz runs are ran. I say "normal" because at that point shrinking occurs, where the test is run more times to find the smallest fuzz input value(s) that still trigger the failure. Perhaps the feature request here is to turn off shrinking to see failures faster? You could probably argue the shrinked values would make debugging faster so it's worth the wait, so I'm curious if a feature to turn off shrinking is useful |
I am experiencing same issues when running large invariant test suite (bunch of invariants + runs + big depth), would be great to have the option to turn off shrinking. Thank you |
@grandizzy created #4867 to track |
Component
Other (please describe)
Describe the feature you would like
When writing fuzzing tests I often find myself waiting for the all fuzzing to end before being able to see the "bug". It sort of make the
debug => fix => run test => debug => fix => run test
process quite painfull when working on a failing test case with fuzzing.Would be super cool to be able to specify somehow that I'd like the fuzzer to abort fuzzing when a test fails. Could be in the command line as an additional parameter or in the
[fuzz]
section of thefoundry.toml
file.Additional context
No response
The text was updated successfully, but these errors were encountered: