Consider dynamically created mocks when pre minimizing fuzzer output and properly initialize @Mock fields #2569
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
When fuzzer executions are pre minimized we should consider mocks that we were added during concrete executions for methods that were actually invoked, but whose behavior wasn't defined by the fuzzer itself.
Also, makes fixes field initialization (when creating
@InjectMock
field we should not mark@Mock
fields as initialized).How to test
Manual tests
Add the following method to
OrderService
inspring-boot-testing
project and generate unit tests, using "Mock everything outside the class" mock strategy and100%
fuzzing.There should be test with real list:
There should be no tests with mocked lists:
Self-check list