-
Notifications
You must be signed in to change notification settings - Fork 59
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 property-based fuzz test #81
Conversation
A test is added that runs mccabe against plenty of random yet valid Python source code. Right now, the test does not do much - it only tests whether mccabe accepts the code. Already this is an achievement because now weird edge cases are covered. Having this test suite integrated will also allow to build up on that. The author of Hypothesis claimed to work on a coverage guided test runner. Also more general properties to hold on any valid source code now can be tested.
Great! Thank you very much. If you would send me a patch I would apply it so you get credits and authorship. |
I do not know how to generate a patch and I do not need credit so please try to apply these changes on your end. My sense is that |
The commited suggestions will restore compatibility with Python 3.6. Co-authored-by: Christian Clauss <cclauss@me.com>
Closing and re-opening to trigger a new merged build on travis |
A test is added that runs mccabe against plenty of random yet valid
Python source code. Right now, the test does not do much - it only tests
whether mccabe accepts the code. Already this is an achievement because
now weird edge cases are covered.
Having this test suite integrated will also allow to build up on that.
The author of Hypothesis claimed to work on a coverage guided test
runner. Also more general properties to hold on any valid source code
now can be tested.