UtBotFieldModificatorsSearcher fixed for default package and public fields #1037
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
volivan239
approved these changes
Sep 30, 2022
|
Replaced with a nornal fix, not like this. |
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.
Description
Searcher of field modificators fixed for default package: in the previous implementation it considered all modificators appropriate if they are located in a default package.
Also public fields validation corrected.
Fixes # (1024)
Type of Change
How Has This Been Tested?
Automated Testing
UtBotFieldModificatorsTest
Manual Scenario
Repeat the scenario described in the mentioned feature with fuzzer and concrete executor turned off.