Mockito Verify method arguments

Question

I ve googled about this  but didn t find anything relevant  I ve got something like this   Object obj   getObject    Mockeable mock  Mockito mock Mockeable class   Mockito when mock mymethod obj    thenReturn null    Testeable testableObj   new Testeable    testableObj setMockeable mock   command runtestmethod      Now  I want to verify that mymethod Object o   which is called inside runtestmethod    was called with the Object o  not any other  But I always pass the test  whatever I put on the verification  for example  with   Mockito verify mock mymethod Mockito eq obj       or  Mockito verify mock mymethod Mockito eq null       or  Mockito verify mock mymethod Mockito eq  something else        I always pass the test  How can I accomplish that verification  if possible     Thank you

User · Answer

Have you tried it with the same   matcher  As in   verify mockObj  someMethod same specificInstance      I had the same problem  I tried it with the eq   matcher as well as the refEq   matcher but I always had false positives  When I used the same   matcher  the test failed when the arguments were different instances and passed once the arguments were the same instance

User · Answer

I have used Mockito verify in this way   UnitTest public class JUnitServiceTest        Mock     private MyCustomService myCustomService         Test     public void testVerifyMethod                Mockito verify myCustomService  Mockito never    mymethod parameters      method will never call  an alternative can be pick to use times 0          Mockito verify myCustomService  Mockito times 2   mymethod parameters      method will call for 2 times        Mockito verify myCustomService  Mockito atLeastOnce    mymethod parameters      method will call atleast 1 time        Mockito verify myCustomService  Mockito atLeast 2   mymethod parameters      method will call atleast 2 times        Mockito verify myCustomService  Mockito atMost 3   mymethod parameters      method will call at most 3 times        Mockito verify myCustomService  Mockito only    mymethod parameters        no other method called except this

User · Answer

Are you trying to do logical equality utilizing the object s  equals method  You can do this utilizing the argThat matcher that is included in Mockito  import static org mockito Matchers argThat   Next you can implement your own argument matcher that will defer to each objects  equals method  private class ObjectEqualityArgumentMatcher lt T gt  extends ArgumentMatcher lt T gt        T thisObject       public ObjectEqualityArgumentMatcher T thisObject            this thisObject   thisObject              Override     public boolean matches Object argument            return thisObject equals argument             Now using your code you can update it to read     Object obj   getObject    Mockeable mock  Mockito mock Mockeable class   Mockito when mock mymethod obj   thenReturn null    Testeable obj   new Testeable    obj setMockeable mock   command runtestmethod     verify mock  mymethod argThat new ObjectEqualityArgumentMatcher lt Object gt  obj       If you are just going for EXACT equality  same object in memory   just do  verify mock  mymethod obj     This will verify it was called once

User · Answer

Many of the above answers confused me but I suspect it may be due to older versions of Mockito  This answer is accomplished using  Java 11 Mockito 3 1 0 SpringBoot 2 2 7 RELEASE JUnit5  Using ArgumentCaptor I have done it this way   Mock MyClientService myClientService   InjectMocks  MyService myService     Test void myTest        ArgumentCaptor lt String gt  captorParam1   ArgumentCaptor forClass String class     ArgumentCaptor lt String gt  captorParam2   ArgumentCaptor forClass String class      Mockito when myClientService doSomething captorParam1 capture    captorParam2 capture    ArgumentMatchers anyString            thenReturn expectedResponse      assertDoesNotThrow    - gt  myService process data       assertEquals  quot param1 quot   captorParam1 getValue       assertEquals  quot param2 quot   captorParam2 getValue        verify myClientService  times 1        doSomething anyString    anyString    anyString

User · Answer

An alternative to ArgumentMatcher is ArgumentCaptor   Official example   ArgumentCaptor lt Person gt  argument   ArgumentCaptor forClass Person class   verify mock  doSomething argument capture     assertEquals  John   argument getValue   getName       A captor can also be defined using the  Captor annotation     Captor ArgumentCaptor lt Person gt  captor        MockitoAnnotations initMocks this    Test public void test                   verify mock  doSomething captor capture         assertEquals  John   captor getValue   getName

User · Answer

Have you checked the equals method for the mockable class  If this one returns always true or you test the same instance against the same instance and the equal method is not overwritten  and therefor only checks against the references   then it returns true

User · Answer

Verify a  aFunc eq b    In pseudocode   When in the instance a - a function named aFunc is called  Verify this call got an argument which is equal to b

User · Answer

The other method is to use the org mockito internal matchers Equals Equals method instead of redefining one     verify myMock  myMethod  inputObject Mockito argThat new Equals inputObjectWanted

User · Answer

You can also use TypeSafeDiagnosingMatcher      private Matcher lt GetPackagesRequest gt  expectedPackageRequest final AvailabilityRequest request        return new TypeSafeDiagnosingMatcher lt GetPackagesRequest gt               StringBuilder text   new StringBuilder 500             Override         protected boolean matchesSafely GetPackagesRequest req  Description desc                String productCode   req getPackageIds   iterator   next   getValue                if  productCode equals request getSupplierProductCode                       text append  ProductCode not equal      productCode           request getSupplierProductCode                     return true                             text append req toString                 return false                      Override         public void describeTo Description d                d appendText text toString                          Then verify that invocation   Mockito verify client  getPackages Mockito argThat expectedPackageRequest request

User · Answer

argThat plus lambda that is how you can fail your argument verification      verify mock  mymethod argThat         x - gt false          where import static org mockito ArgumentMatchers argThat  import static org mockito Mockito verify    argThat plus asserts the above test will  quot say quot  Expected  lambda     Was  YourClass toSting     You can get a more specific cause of the failure if to use asserts in the the lambda      verify mock  mymethod argThat  x - gt          assertThat x  isNotNull          assertThat x description  contains  quot KEY quot          return true              BUT    THIS ONLY WORKS WHEN  THE CALL IS EXPECTED 1 TIME  or the call is expected 2  times  but all the times the verifier matches  returns true    If the verified method called 2  times  mockito passes all the called combinations to each verifier  So mockito expects your verifier silently returns true for one of the argument set  and false  no assert exceptions  for other valid calls  That expectation is not a problem for 1 method call - it should just return true 1 time  import static org assertj core api Assertions assertThat  import static org mockito ArgumentMatchers argThat  import static org mockito Mockito verify   Now the failed test will say  Expected  Obj description to contain  KEY   Was   Actual description   NOTE  I used assertJ asserts  but it s up to you which assertion framework to use   argThat with multiple arguments  If you use argThat  all arguments must be provided with matches  E g       verify mock  mymethod eq  quot VALUE 1 quot    argThat  x - gt false           above is correct as eq   is also an argument matcher    verify mock  mymethod  quot VALUE 1 quot   argThat  x - gt false       above is incorrect  an exceptoin will be thrown  as the fist arg  is given without an argument matcher   where  import static org mockito ArgumentMatchers argThat  import static org mockito ArgumentMatchers eq  import static org mockito Mockito verify    eq matcher the easiest way to check if the argument is equal  verify mock  mymethod eq expectedValue       NOTE      where the parentheses must be closed    direct argument if comparison by ref is acceptable  then go on with  verify mock  mymethod expectedArg      NOTE      where the parentheses must be closed    THE ROOT CAUSE of original question failure was the wrong place of the paranthes  verify mock mymethod     That was wrong  The right would be  verify mock

User · Answer

You don t need the eq matcher if you don t use other matchers  You are not using the correct syntax - your method call should be outside the  verify mock   You are now initiating verification on the result of the method call  without verifying anything  not making a method call   Hence all tests are passing    You code should look like   Mockito verify mock  mymethod obj   Mockito verify mock  mymethod null   Mockito verify mock  mymethod  something else

[java] Mockito. Verify method arguments

Examples related to java

Examples related to unit-testing

Examples related to junit

Examples related to mockito