Mockito 验证无法正常工作答案

【问题标题】：Mockito verify not working correctlyMockito 验证无法正常工作
【发布时间】：2018-08-01 12:56:52
【问题描述】：

我对 Mockito 还是很陌生，尽管我之前已经成功运行过测试，但今天看起来很奇怪为什么 mockito verify() 方法一直告诉我需要 View 方法，但即使我确定也没有调用Presenter 方法调用正确。这是我的测试代码：

 @Test
public void loadCallPlans_shouldUpdateAdapter() {
    ArrayResponse<CallPlan> callPlans = new ArrayResponse<>();
    callPlans.data = Arrays.asList(new CallPlan[]{new CallPlan(), new CallPlan()});
    Single response = Single.just(callPlans);

    when(callPlanRepository.getCallPlans()).thenReturn(response);

    presenter.loadCallPlans("Today");

    doAnswer((Answer<Void>) invocation -> {
        Object[] args = invocation.getArguments();
        System.out.println("View.updateCallPlans() called with arguments: " + java.util.Arrays.toString(args));
        return null;
    }).when(view).updateCallPlans(anyList());

    verify(view).updateCallPlans(anyList());

}

我可以确认调用了 updateCallPlans() 方法，因为我在 logcat 中得到了 View.updateCallPlans() called with arguments: [[]]。我的完整日志：

View.updateCallPlans() called with arguments: [[]]


Wanted but not invoked:
view.updateCallPlans(<any List>);
-> at    CallPlansPresenterTest.loadCallPlans_should    UpdateAdapter(CallPlansPresenterTest.java:69)
Actually, there were zero interactions with this mock.

Wanted but not invoked:
view.updateCallPlans(<any List>);
-> at     CallPlansPresenterTest.loadCallPlans_should    UpdateAdapter(CallPlansPresenterTest.java:69)
Actually, there were zero interactions with this mock.

at CallPlansPresenterTest.loadCallPlans_shouldUpdateAdapter(CallPlansPresenterTest.java:69)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.junit.internal.runners.TestMethod.invoke(TestMethod.java:68)
at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl$PowerMockJUnit44MethodRunner.runTestMethod(PowerMockJUnit44RunnerDelegateImpl.java:326)
at org.junit.internal.runners.MethodRoadie$2.run(MethodRoadie.java:89)
at org.junit.internal.runners.MethodRoadie.runBeforesThenTestThenAfters(MethodRoadie.java:97)
at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl$PowerMockJUnit44MethodRunner.executeTest(PowerMockJUnit44RunnerDelegateImpl.java:310)
at org.powermock.modules.junit4.internal.impl.PowerMockJUnit47RunnerDelegateImpl$PowerMockJUnit47MethodRunner.executeTestInSuper(PowerMockJUnit47RunnerDelegateImpl.java:131)
at org.powermock.modules.junit4.internal.impl.PowerMockJUnit47RunnerDelegateImpl$PowerMockJUnit47MethodRunner.access$100(PowerMockJUnit47RunnerDelegateImpl.java:59)
at org.powermock.modules.junit4.internal.impl.PowerMockJUnit47RunnerDelegateImpl$PowerMockJUnit47MethodRunner$TestExecutorStatement.evaluate(PowerMockJUnit47RunnerDelegateImpl.java:147)
at org.powermock.modules.junit4.internal.impl.PowerMockJUnit47RunnerDelegateImpl$PowerMockJUnit47MethodRunner.evaluateStatement(PowerMockJUnit47RunnerDelegateImpl.java:107)
at org.powermock.modules.junit4.internal.impl.PowerMockJUnit47RunnerDelegateImpl$PowerMockJUnit47MethodRunner.executeTest(PowerMockJUnit47RunnerDelegateImpl.java:82)
at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl$PowerMockJUnit44MethodRunner.runBeforesThenTestThenAfters(PowerMockJUnit44RunnerDelegateImpl.java:298)
at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:87)
at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:50)
at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.invokeTestMethod(PowerMockJUnit44RunnerDelegateImpl.java:218)
at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.runMethods(PowerMockJUnit44RunnerDelegateImpl.java:160)
at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl$1.run(PowerMockJUnit44RunnerDelegateImpl.java:134)
at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:34)
at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:44)
at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.run(PowerMockJUnit44RunnerDelegateImpl.java:136)
at org.powermock.modules.junit4.common.internal.impl.JUnit4TestSuiteChunkerImpl.run(JUnit4TestSuiteChunkerImpl.java:121)
at org.powermock.modules.junit4.common.internal.impl.AbstractCommonPowerMockRunner.run(AbstractCommonPowerMockRunner.java:57)
at org.powermock.modules.junit4.PowerMockRunner.run(PowerMockRunner.java:59)
at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
at com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.intellij.rt.execution.application.AppMainV2.main(AppMainV2.java:131)

如果我让 RxJava 返回错误作为响应，则测试运行良好并且 View.setError() 已正确验证：

 @Test
 public void loadCallPlans_shouldShowError() {
    String error = "Error";
    Single response = Single.error(new Throwable(error));

    when(callPlanRepository.getCallPlans()).thenReturn(response);

    presenter.loadCallPlans("Today");

    doAnswer((Answer<Void>) invocation -> {
        Object[] args = invocation.getArguments();
        System.out.println("View.setError() called with arguments: " + java.util.Arrays.toString(args));
        return null;
    }).when(view).setError(anyString());

    verify(view).setError(error);

}

【问题讨论】：

不，你没有“在 logcat 中得到View.updateCallPlans() called with arguments: [[]]”；你会在 logcat 中得到 View.populateItemsAdapter() called with arguments: [[]]。
@daniu 这是一个错字，应该是View.updateCallPlans()，我已将问题更新到正确的日志中。谢谢。
presenter.loadCallPlans 返回什么类型？
@JakubCh。它什么也不返回（Void）

标签： java android mockito junit4

【解决方案1】：

您实际上是在模拟对 updateCallPlans 的调用

doAnswer((Answer<Void>) invocation -> {
        Object[] args = invocation.getArguments();
        System.out.println("View.updateCallPlans() called with arguments: " + java.util.Arrays.toString(args));
        return null;
    }).when(view).updateCallPlans(anyList());
}

所以它永远不会调用实际的方法。

您的验证应该在答案调用中。

【讨论】：

嗨，Harshal，我不是在嘲笑 updateCallPlans，我只是在 mockito 调用它时将要执行的代码存根，以验证它是否被实际调用，如果我仍然得到相同的结果我删除它。
同意你的观点，你正在存根方法。并且您期望在 updateCallPlans 上实际调用 1 次，而这并没有发生。当您将verify(view).updateCallPlans(anyList()); 替换为view.updateCallPlans(anyList()); 时，测试将通过。
我似乎不明白你，但我需要 mockito 来验证该方法是否被调用，这是编写测试的主要原因，view.updateCallPlans(anyList()); 不会为我这样做。

【解决方案2】：

只是想把它放在这里以防有人遇到同样的问题，我不知道 AndroidSchedulers 是 mockito 的脏类，所以我直接在我的演示者中使用它，而不是创建一个提供通过构造函数需要调度程序。更多解释来自here

【讨论】：