Use Mockito to mock some methods but not others

by

To directly answer your question, yes, you can mock some methods without mocking others. This is called a partial mock. See the Mockito documentation on partial mocks for more information.

For your example, you can do something like the following, in your test:

Stock stock = mock(Stock.class);
when(stock.getPrice()).thenReturn(100.00);    // Mock implementation
when(stock.getQuantity()).thenReturn(200);    // Mock implementation
when(stock.getValue()).thenCallRealMethod();  // Real implementation

In that case, each method implementation is mocked, unless specify thenCallRealMethod() in the when(..) clause.

There is also a possibility the other way around with spy instead of mock:

Stock stock = spy(Stock.class);
when(stock.getPrice()).thenReturn(100.00);    // Mock implementation
when(stock.getQuantity()).thenReturn(200);    // Mock implementation
// All other method call will use the real implementations

In that case, all method implementation are the real one, except if you have defined a mocked behaviour with when(..).

There is one important pitfall when you use when(Object) with spy like in the previous example. The real method will be called (because stock.getPrice() is evaluated before when(..) at runtime). This can be a problem if your method contains logic that should not be called. You can write the previous example like this:

Stock stock = spy(Stock.class);
doReturn(100.00).when(stock).getPrice();    // Mock implementation
doReturn(200).when(stock).getQuantity();    // Mock implementation
// All other method call will use the real implementations

Another possibility may be to use org.mockito.Mockito.CALLS_REAL_METHODS, such as:

Stock MOCK_STOCK = Mockito.mock( Stock.class, CALLS_REAL_METHODS );

This delegates unstubbed calls to real implementations.

However, with your example, I believe it will still fail, since the implementation of getValue() relies on quantity and price, rather than getQuantity() and getPrice(), which is what you’ve mocked.

Another possibility is to avoid mocks altogether:

@Test
public void getValueTest() {
    Stock stock = new Stock(100.00, 200);
    double value = stock.getValue();
    assertEquals("Stock value not correct", 100.00*200, value, .00001);
}

More Related Contents:

  1. Mocking static methods with Mockito
  2. How to mock void methods with Mockito
  3. Difference between @Mock and @InjectMocks
  4. Using Mockito to test abstract classes
  5. How do Mockito matchers work?
  6. Using Mockito with multiple calls to the same method with the same arguments
  7. How to properly match varargs in Mockito
  8. Final method mocking
  9. Mock a constructor with parameter
  10. How to tell a Mockito mock object to return something different the next time it is called?
  11. Is it possible to use Mockito in Kotlin?
  12. How to mock new Date() in java using Mockito
  13. Is it discouraged to use @Spy and @InjectMocks on the same field?
  14. Unfinished Stubbing Detected in Mockito
  15. Mockito – @Spy vs @Mock
  16. What is the difference between mocking and spying when using Mockito?
  17. mock or stub for chained call
  18. Mockito test a void method throws an exception
  19. junit testing for user input using Scanner
  20. Why is my class not calling my mocked methods in unit test?
  21. throw checked Exceptions from mocks with Mockito
  22. Why are my mocked methods not calld when executing a unit test?
  23. Forming Mockito “grammars”
  24. Why are my mocked methods not called when executing a unit test?
  25. Mockito – difference between doReturn() and when()
  26. How to use Mockito with JUnit5
  27. Testing Private method using mockito
  28. mocking a method that return generics with wildcard using mockito
  29. java: how to mock Calendar.getInstance()?
  30. Integration tests for AspectJ

Leave a Comment