-
Notifications
You must be signed in to change notification settings - Fork 3
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 fuzz tests #112
Labels
Comments
henryso
added a commit
to henryso/gregorio-test
that referenced
this issue
Jan 31, 2016
henryso
added a commit
to henryso/gregorio-test
that referenced
this issue
Feb 1, 2016
henryso
added a commit
to henryso/gregorio-test
that referenced
this issue
Feb 1, 2016
henryso
added a commit
to henryso/gregorio-test
that referenced
this issue
Feb 2, 2016
henryso
added a commit
to henryso/gregorio-test
that referenced
this issue
Feb 2, 2016
Merged
henryso
added a commit
to henryso/gregorio-test
that referenced
this issue
Feb 3, 2016
henryso
added a commit
to henryso/gregorio-test
that referenced
this issue
Feb 4, 2016
henryso
added a commit
to henryso/gregorio-test
that referenced
this issue
Feb 7, 2016
Why closing this? I don't think we have randomly generated tests? |
Sorry, I misunderstood what you wanted here. |
It was raised in a comment from the C security issue, these tests obviously wouldn't have some expected results, I think it's mainly to test some incoherent states or segfaults... I don't think it's a high priority |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See this comment, the idea is to give gregorio some random characters, and random more or less valid gabc and nabc, to check that no crash happens
The text was updated successfully, but these errors were encountered: