Skip to content

Conversation

@ARMS2025
Copy link

@ARMS2025 ARMS2025 commented Feb 21, 2025

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

  1. getDirective was executed with arguments "edgeTarget", but was not stubbed, resulting in a mismatch stubbing, this mismatch occurs in the test processWithTraversal.

  2. get was executed with arguments "Document/1" but was not stubbed, resulting in a mismatch stubbing, this mismatch occurs in the test processWithTraversal.

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).

We propose a solution below to resolve the mismatch stubbings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant