Java EasyMock 3和一个类：

我正试图模仿这样一个类（感谢谷歌的代码设计，它很难在测试环境中使用）：

然后我将设置一个模拟方法调用，如下所示：

AccessTokenResponse accessTokenResponse = new AccessTokenResponse();
EasyMock.expect(googleAuthorizationCodeGrant.execute()).andReturn(accessTokenResponse);

但它会说出一个异常，因为在googleAuthorizationCodeGrant.execute（）期间，它会尝试运行googleAuthorizationCodeGrant.execute（）中的实际代码。我是不是遗漏了什么？我希望cglib代理包装这个类并重写它的方法，使其不做任何事情，因为我不希望在模拟时实现它们。应该不需要保留任何业务逻辑，因为我正在定义各种方法调用的行为

编辑

注意-我认为这里有些混乱。在以下情况下引发异常：

EasyMock.expect(googleAuthorizationCodeGrant.execute()).andReturn(accessTokenResponse)

当我把模拟放在重播模式时就不会了，因为我从来没有真正接触过那个代码。引发异常的原因是，GoogleAuthorizationCodeGrant的一个成员为null，并且在.execute（）上对其调用了一个方法。如果我使用新运算符实例化了GoogleAuthorizationCodeGrant，则该成员不会为null。但是，我不明白为什么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)

---

我不确定你是否重播了那个模拟的实例。如果您已经这样做了，但仍然得到异常，请将堆栈跟踪添加到问题中。

是否可以将异常中的堆栈跟踪添加到问题中？是否已将模拟对象设置为replay状态？在AccessTokenRequest行451中，您是否调用googleAuthorizationCodeGrant.execute（）方法，如果是这样，您是否已将模拟的GoogleAuthorizationCodeGrant注入AccessTokenRequest类中。如果没有，它将调用原始的GoogleAuthorizationCodeGrant代码。即使EasyMock已经为这个类创建了代理，您也需要将这个mock传递给调用类，这样原始的GoogleAuthCodeGrant就不会被执行。

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)