Resolved mismatch stubbings in PropertySetterTaskTest.java #384

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Open

ARMS2025 wants to merge 1 commit into labsai:main from ARMS2025:resolve-mismatch-stubbings-1

ARMS2025 commented May 12, 2025 •

edited by ginccc

Loading

I analyzed the test doubles (mocks) in the test code of the project. In my analysis of the project, I observed that

In the test executeTask:

the getLatestData method for the currentStep object:
i) during test execution the method is called with argument "actions", but is not stubbed, resulting in a mismatch stubbing.

In general, a mismatched stubbing occurs when a method is stubbed with specific arguments in a test but later invoked with different arguments in the code. Mockito recommends addressing this type of issue (https://www.javadoc.io/doc/org.mockito/mockito-core/latest/org.mockito/org/mockito/exceptions/misusing/PotentialStubbingProblem.html).

I propose a solution below to resolve the mismatch stubbing. Happy to modify the pull request based on your feedback.

This change is


          Resolve mismatch stubbings in PropertySetterTaskTest.java

18071b2

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

Labels

None yet