How to verify that a specific method was not called using Mockito

Question

How to verify that a method is not called on an object s dependency   For example   public interface Dependency       void someMethod       public class Foo       public bar final Dependency d                          With the Foo test   public class FooTest        Test     public void dependencyIsNotCalled             final Foo foo   new Foo               final Dependency dependency   mock Dependency class           foo bar dependency                verify here that someMethod was not called

User · Answer

Use the second argument on the Mockito verify method  as in  Mockito verify dependency  Mockito times 0   someMethod

User · Answer

Both the verifyNoMoreInteractions   and verifyZeroInteractions   method internally have the same implementation as   public static transient void verifyNoMoreInteractions Object mocks          MOCKITO CORE verifyNoMoreInteractions mocks      public static transient void verifyZeroInteractions Object mocks          MOCKITO CORE verifyNoMoreInteractions mocks       so we can use any one of them on mock object or array of mock objects to check that no methods have been called using mock objects

User · Answer

First of all  you should always import mockito static  this way the code will be much more readable  and intuitive    import static org mockito Mockito      There are actually many ways to achieve this  however it s  arguably  cleaner to use the   verify yourMock  times 0   someMethod      method all over your tests  when on other Tests you use it to assert a certain amount of executions like this   verify yourMock  times 5   someMethod      Alternatives are   verify yourMock  never    someMethod      Alternatively - when you really want to make sure a certain mocked Object is actually NOT called at all - you can use   verifyZeroInteractions yourMock

User · Answer

As a more general pattern to follow  I tend to use an  After block in the test    After public void after         verifyNoMoreInteractions  lt your mock1 gt    lt your mock2 gt           Then the test is free to verify only what should be called   Also  I found that I often forgot to check for  no interactions   only to later discover that things were being called that shouldn t have been   So I find this pattern useful for catching all unexpected calls that haven t specifically been verified

User · Answer

Even more meaningful    import static org mockito Mockito never  import static org mockito Mockito verify           verify dependency  never    someMethod      The documentation of this feature is there   4  Verifying exact number of invocations   at least x   never   and the never javadoc is here

[java] How to verify that a specific method was not called using Mockito?

Examples related to java

Examples related to tdd

Examples related to mockito