Add disjunction with null condition to isMock constraint #1521
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
CaelmBleidd
force-pushed
the
caelmbleidd/null_values_as_mock_fix
branch
from
55e5eec to
fda8e9f
Compare
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
Added a disjunction with nullability constraint to avoid an assignment to a null object contradicting conditions about whether it is mock or not.
Fixes #1520
Type of Change
How Has This Been Tested?
Regression and integration tests
There is no difference between automatic tests and international tests for the engine.
Automated Testing
org.utbot.examples.mock.CommonMocksExample#mocksForNullOfDifferentTypes
Manual Scenario
Did not check it manually.
Checklist: