Report failing fuzz tests #15
Merged
Conversation
This file contains hidden or 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
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.
Previously fuzz test results were just completely ignored, which makes sense if you think of
gotestdoxas a documentation-generating tool. Fuzz cases are autogenerated and don't tend to have names that would be interesting as sentences.But if you use
gotestdoxas a test runner, then we have to take into account that fuzz cases can fail. In that case, it's helpful to see what's failing and why.So, the compromise solution that everyone will hate is that
gotestdoxnow reports fuzz test names, but only if they're failing.