Skip to content
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

Recognize, and stop fuzzing, when a test is exhausted #12

Open
Zac-HD opened this issue Oct 30, 2022 · 0 comments
Open

Recognize, and stop fuzzing, when a test is exhausted #12

Zac-HD opened this issue Oct 30, 2022 · 0 comments

Comments

@Zac-HD
Copy link
Owner

Zac-HD commented Oct 30, 2022

Hypothesis can detect when a strategy is exhausted, i.e. when all possible values have been tested, and will stop early in that case. For unit-testing-like workloads this typically only happens for simple strategies such as st.booleans() or small ranges of st.integers(), but in a long fuzzing run it could conceivably happen for considerably larger sets of values.

While not a high priority, it would be nice to implement this for HypoFuzz if it's possible to do so without consuming too much memory.

See: https://mboehme.github.io/paper/ICSE23.Effectiveness.pdf

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant