Many similar sandboxed tests on sockets generated by Fuzzing and not minimized #1129 #1132
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.
Description
There's no coverage trace when error occurs before the method is invoked. Therefore, fuzzer generates too many values which are not minimized later. To fix this issue fuzzer now compares stack traces of the error to minimize test number.
Similar behavior can be implemented in other places.
Fixes #1129
Type of Change
How Has This Been Tested?
Automated Testing
All fuzzer tests should work
Manual Scenario
Reproduces the example from the issue. After the fix only 8 tests should be found.
Checklist: