Mockito在spring的间谍对象

当我尝试在unit testing中窥探一个对象时,我得到了一个例外。 这是我的unit testing文件:

@RunWith(SpringJUnit4ClassRunner.class) @ContextConfiguration(locations = { "classpath:spring/applicationContext.xml" }) public class BookingSuperManTest { BookInfoParams bookInfoParams; HttpAttributeParams httpAttributeParams; AbstractRequester requester; public void beforeStartTest(){ bookInfoParams = Mockito.spy(new BookInfoParams()); httpAttributeParams = Mockito.spy(new HttpAttributeParams()); } @Test public void step1GoToHomePage() throws BookingException{ beforeStartTest(); requester = new Step1HomePage(bookInfoParams, httpAttributeParams); requester.executeRequest(); Assert.assertNotNull(httpAttributeParams.getResponseGetRequest()); } } 

我在链接分配bookInfoParams spy时得到了exception:

 java.lang.NoClassDefFoundError: org/mockito/cglib/proxy/MethodInterceptor at org.powermock.api.mockito.internal.mockmaker.PowerMockMaker.(PowerMockMaker.java:43) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at java.lang.Class.newInstance(Class.java:379) at org.mockito.internal.configuration.plugins.PluginLoader.loadImpl(PluginLoader.java:61) at org.mockito.internal.configuration.plugins.PluginLoader.loadPlugin(PluginLoader.java:24) at org.mockito.internal.configuration.plugins.PluginRegistry.(PluginRegistry.java:13) at org.mockito.internal.configuration.plugins.Plugins.(Plugins.java:12) at org.mockito.internal.util.MockUtil.(MockUtil.java:23) at org.mockito.internal.MockitoCore.(MockitoCore.java:40) at org.mockito.Mockito.(Mockito.java:1103) at ive.core.test.webbot.book.vietjet.BookingSuperManTest.beforeStartTest(BookingSuperManTest.java:46) at ive.core.test.webbot.book.vietjet.BookingSuperManTest.step1GoToHomePage(BookingSuperManTest.java:54) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) 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.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:73) at org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:82) at org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:73) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:224) at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:83) 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.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61) at org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:68) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:163) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192) Caused by: java.lang.ClassNotFoundException: org.mockito.cglib.proxy.MethodInterceptor at java.net.URLClassLoader$1.run(URLClassLoader.java:366) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at java.lang.ClassLoader.loadClass(ClassLoader.java:425) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) ... 44 more 

这是我的pom文件中的依赖项

  junit junit 4.12   org.mockito mockito-core 2.0.44-beta   org.powermock powermock-api-mockito 1.6.4   org.powermock powermock-module-junit4 1.6.4   cglib cglib 3.2.1 test  

也许版本不兼容或我错过了什么?

它可能是依赖项的问题。 powermock-api-mockitomockito-core版本1.10.19上有编译时依赖性,但你也定义了对版本2.0.44-beta的依赖。 这可能是类路径问题。 尝试删除版本2.0.44-beta的显式依赖2.0.44-beta

在2.0.32-beta版本中,Mockito团队将cglib类移到了分离的jar中 。 但是PowerMock仍然依赖于已移动的类,因此您将获得java.lang.NoClassDefFoundError。

在版本1.6.2中,Mockito类被复制到PowerMock中,但并非全部。 作为解决方法,我可能建议克隆,构建并添加到类路径mockito-cglib( https://github.com/mockito/mockito-cglib )。

从1.6.5开始,PowerMock将支持 Mockito 2 API,它将在5月底发布,但仍将使用cglib。 完整的Mockito 2和Bytebuddy将在1.6.5之后发布。

移植到Mockito的开发人员指南2

这是因为powermock-api-mockito对mockito-core的依赖性。 由于powermock-api-mockito被明确添加为依赖项,请删除mockito-core,这可能会导致问题