当从基类中删除方法时,Mockito会抛出NPE

时间:2016-12-08 10:44:49

标签: java unit-testing mockito hystrix

我在测试的课程中使用了Hystrix(v.1.5.6)命令,并且我试图用Mockito(v.1.10.19)模拟它。

最近,如果命令因超时而失败,我必须添加特殊行为:

try {
    result = command.execute();
} catch (HystrixRuntimeException err) {
    if (command.isResponseTimedOut()) {
        /** do stuff **/
    }
    /** do stuff **/;
}

这是我的测试类中的代码:

HttpClientCommand command = mock(HttpClientCommand.class);

when(commandFactory.get(anyString(), anyString(), anyString(), anyMapOf(String.class, String.class))).thenReturn(command);
when(command.execute()).thenThrow(hystrixRuntimeException);
when(command.isResponseTimedOut()).thenReturn(false);

我的HttpClientCommand扩展了HystrixCommand课程。 execute方法在这个类中,我没有问题。

HystrixCommand类然后扩展AbstractCommand类,isResponseTimedOut方法。当我尝试存根时,我从Mockito获得了一个NPE(在when(command.isResponseTimedOut()).thenReturn(false);行,在我测试的类上调用任何方法之前)。

堆栈追踪:

java.lang.Exception: Unexpected exception, expected<my.custom.exception> but was<java.lang.NullPointerException>

    at org.junit.internal.runners.statements.ExpectException.evaluate(ExpectException.java:28)
    at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
    at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
    at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
    at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
    at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
    at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
    at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
    at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
    at org.mockito.internal.runners.JUnit45AndHigherRunnerImpl.run(JUnit45AndHigherRunnerImpl.java:37)
    at org.mockito.runners.MockitoJUnitRunner.run(MockitoJUnitRunner.java:62)
    at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
    at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:117)
    at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:42)
    at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:262)
    at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:84)
    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:497)
    at com.intellij.rt.execution.application.AppMain.main(AppMain.java:147)
Caused by: java.lang.NullPointerException
    at com.netflix.hystrix.AbstractCommand.isResponseTimedOut(AbstractCommand.java:1809)
    at com.netflix.hystrix.HystrixCommand.isResponseTimedOut(HystrixCommand.java:46)
    at com.myClassTest.testGetLocation_shouldThrowCustomException_whenRequestException(myClassTest.java:300)
    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:497)
    at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
    at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
    at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
    at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
    at org.junit.internal.runners.statements.ExpectException.evaluate(ExpectException.java:19)
    ... 22 more

如何保存此方法?

1 个答案:

答案 0 :(得分:1)

好的问题是由于CGLIB的错误,mockito 1.x使用了CGLIB。当模拟的方法在非公共父级中声明时,CGLIB不拦截该方法,因此它执行实际代码。我们的旧问题跟踪器仍然可以使用此问题:issue 212

两个选项:

  1. HttpHystrixCommand中编写一个将调用super方法的公共重载,但由于abstract命令有很多处理失败的方法,因此这不是一个可以扩展得很好的选项。 / p>

  2. 使用mockito 2.我们与ByteBuddy的开发者--Rafel Winterhalter合作 - 取代CGLIB。 ByteBuddy没有像CGLIB那样多年来几乎被遗弃的缺点。当前版本是2.2.29,并且在此时发布定期更新。