我试图嘲弄一类像这样(感谢的谷歌代码的设计,很难在测试环境中使用):EasyMock的3类:
GoogleAuthorizationCodeGrant googleAuthorizationCodeGrant = EasyMock.createMock(GoogleAuthorizationCodeGrant.class);
然后我设立一个模拟的方法调用像这样:
AccessTokenResponse accessTokenResponse = new AccessTokenResponse();
EasyMock.expect(googleAuthorizationCodeGrant.execute()).andReturn(accessTokenResponse);
然而,它喷出的例外,因为googleAuthorizationCodeGrant.execute(中)它会尝试在googleAuthorizationCodeGrant.execute运行的实际代码()。我在这里错过了什么吗?我期望cglib代理包装这个类,并覆盖它的方法什么也不做,因为我不希望它们在模拟时执行。应该不需要保留任何业务逻辑,因为我正在定义各种方法调用的行为。
编辑
注 - 我认为这里存在一些混乱。抛出异常:
EasyMock.expect(googleAuthorizationCodeGrant.execute()).andReturn(accessTokenResponse)
不是当我把模拟放在重放模式,因为我从来没有真正达到过这个代码。引发异常的原因是因为GoogleAuthorizationCodeGrant的成员为null,并且在.execute()上对其调用方法。如果我使用new运算符实例化GoogleAuthorizationCodeGrant,则该成员不会为空。然而我不明白为什么EasyMock会像这样在一个类上工作,因为我期望它创建一个代理来封装实现,从而无需执行任何操作。
这里是一个堆栈跟踪:
java.lang.NullPointerException
at com.google.api.client.auth.oauth2.draft10.AccessTokenRequest.executeUnparsed(AccessTokenRequest.java:451)
at com.google.api.client.auth.oauth2.draft10.AccessTokenRequest.execute(AccessTokenRequest.java:475)
at uk.co.domain.service.google.GmailContactPollerTest.testDoPoll(GmailContactPollerTest.java:64)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
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:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
你能否将异常的堆栈跟踪添加到问题中? – Alb 2012-02-29 16:24:28
您是否将模拟对象设置为重播状态? – 2012-03-09 04:31:42