另一个可能导致间谍问题的场景是，当您测试spring bean(使用spring测试框架)或在测试期间探查对象的其他框架时。

例子

@Autowired
private MonitoringDocumentsRepository repository

void test(){
    repository = Mockito.spy(repository)
    Mockito.doReturn(docs1, docs2)
            .when(repository).findMonitoringDocuments(Mockito.nullable(MonitoringDocumentSearchRequest.class));
}

在上面的代码中，Spring和Mockito都将尝试代理您的MonitoringDocumentsRepository对象，但Spring将首先代理，这将导致findMonitoringDocuments方法的真正调用。如果我们在存储库对象上放置间谍之后调试代码，它将在调试器中看起来像这样:

repository = MonitoringDocumentsRepository$$EnhancerBySpringCGLIB$$MockitoMock$

@SpyBean来拯救

如果改用@Autowired注释，我们使用@SpyBean注释，我们将解决上述问题，SpyBean注释也将注入存储库对象，但它将首先由Mockito代理，并在调试器中看起来像这样

repository = MonitoringDocumentsRepository$$MockitoMock$$EnhancerBySpringCGLIB$

下面是代码:

@SpyBean
private MonitoringDocumentsRepository repository

void test(){
    Mockito.doReturn(docs1, docs2)
            .when(repository).findMonitoringDocuments(Mockito.nullable(MonitoringDocumentSearchRequest.class));
}

有点晚了，但以上的解决方案并不适合我，所以分享我的0.02美元

Mokcito版本:1.10.19

MyClass.java

private int handleAction(List<String> argList, String action)

Test.java

MyClass spy = PowerMockito.spy(new MyClass());

以下没有为我工作(实际的方法正在被调用):

1.

doReturn(0).when(spy , "handleAction", ListUtils.EMPTY_LIST, new String());

2.

doReturn(0).when(spy , "handleAction", any(), anyString());

3.

doReturn(0).when(spy , "handleAction", null, null);

以下工作:

doReturn(0).when(spy , "handleAction", any(List.class), anyString());

在我的例子中，使用Mockito 2.0，我必须将所有any()参数更改为nullable()，以便存根真正的调用。

Tomasz Nurkiewicz的回答似乎并没有说出全部的故事!

NB模仿版本:1.10.19。

我是一个非常多的Mockito新手，所以不能解释以下行为:如果有一个专家在那里谁可以改善这个答案，请随意。

这里讨论的方法getContentStringValue不是最终的，也不是静态的。

这一行调用了原始方法getContentStringValue:

doReturn( "dummy" ).when( im ).getContentStringValue( anyInt(), isA( ScoreDoc.class ));

这一行不调用原始方法getContentStringValue:

doReturn( "dummy" ).when( im ).getContentStringValue( anyInt(), any( ScoreDoc.class ));

由于我无法回答的原因，使用isA()会导致预期的(?)doReturn的“不调用方法”行为失败。

Let's look at the method signatures involved here: they are both static methods of Matchers. Both are said by the Javadoc to return null, which is a little difficult to get your head around in itself. Presumably the Class object passed as the parameter is examined but the result either never calculated or discarded. Given that null can stand for any class and that you are hoping for the mocked method not to be called, couldn't the signatures of isA( ... ) and any( ... ) just return null rather than a generic parameter* <T>?

无论如何:

public static <T> T isA(java.lang.Class<T> clazz)

public static <T> T any(java.lang.Class<T> clazz)

The API documentation does not give any clue about this. It also seems to say the need for such "do not call method" behaviour is "very rare". Personally I use this technique all the time: typically I find that mocking involves a few lines which "set the scene" ... followed by calling a method which then "plays out" the scene in the mock context which you have staged... and while you are setting up the scenery and the props the last thing you want is for the actors to enter stage left and start acting their hearts out...

但这远远超出了我的职权范围…我请路过的Mockito大祭司解释一下…

*“通用参数”是正确的术语吗?

你侦察真实物体的能力很重要

当使用间谍存根一个方法时，请使用doReturn()方法族。

when(Object)将导致调用可以抛出异常的实际方法。

List spy = spy(new LinkedList());

//Incorrect , spy.get() will throw IndexOutOfBoundsException   
 when(spy.get(0)).thenReturn("foo");

//You have to use doReturn() for stubbing    
doReturn("foo").when(spy).get(0);

正如在一些评论中提到的，我的方法是“静态的”(尽管是由类的实例调用的)

public class A {
  static void myMethod() {...}
}
A instance = spy(new A());
verify(instance).myMethod(); // still calls the original method because it's static

解决方法是创建一个实例方法，或者通过一些配置将Mockito升级到一个新版本:https://stackoverflow.com/a/62860455/32453