Resolve 2 mismatch stubbings in KeyValueTest.java #22
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.
We are researchers and analyzed the test doubles (mocks) in the test code of the project. In our analysis of the project, we observed that
getDominValue
method, which is previously stubbed, is executed with arguments "dom1" and "dom2", but these specific arguments are not stubbed, resulting in mismatch stubbings. These mismatches occur in the testwildcardsAlsoMatchNullDomainValues
.In this pull request, we propose a solution to resolve the mismatch stubbing.
Mismatched stubbing occurs when a mocked method is stubbed with specific arguments in a test but later invoked with different arguments in the code, potentially causing unexpected behavior. Mockito recommends addressing these issues, (https://www.javadoc.io/doc/org.mockito/mockito-core/latest/org/mockito/exceptions/misusing/PotentialStubbingProblem.html)