org.mockito.internal.stubbing.answers

Class CallsRealMethods

java.lang.Object

org.mockito.internal.stubbing.answers.CallsRealMethods

All Implemented Interfaces:

Serializable, Answer<Object>

public class CallsRealMethods
extends Object
implements Answer<Object>, Serializable

Optional Answer that adds partial mocking support

Answer can be used to define the return values of unstubbed invocations.

This implementation can be helpful when working with legacy code. When this implementation is used, unstubbed methods will delegate to the real implementation. This is a way to create a partial mock object that calls real methods by default.

As usual you are going to read the partial mock warning: Object oriented programming is more less tackling complexity by dividing the complexity into separate, specific, SRPy objects. How does partial mock fit into this paradigm? Well, it just doesn't... Partial mock usually means that the complexity has been moved to a different method on the same object. In most cases, this is not the way you want to design your application.

However, there are rare cases when partial mocks come handy: dealing with code you cannot change easily (3rd party interfaces, interim refactoring of legacy code etc.) However, I wouldn't use partial mocks for new, test-driven & well-designed code.

See Also:

Serialized Form

Constructor Summary

Constructors

Constructor and Description
CallsRealMethods()

Method Summary

Modifier and Type	Method and Description
Object	answer(InvocationOnMock invocation)

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

CallsRealMethods

public CallsRealMethods()

Method Detail

answer

public Object answer(InvocationOnMock invocation)
              throws Throwable

Specified by:

answer in interface Answer<Object>

Parameters:

invocation - the invocation on the mock.

Returns:

the value to be returned

Throws:

Throwable - the throwable to be thrown