是否可以使用PowerMockRule而不是PowerMockRunner在最终类上模拟静态方法？

Question

根据PowerMock文档,我应该能够使用a PowerMockRule而不是@RunWith(PowerMockRunner.class)得到相同的结果.

我似乎找到了一个不存在这种情况的案例.

以下示例运行良好:

package com.test.powermockstatics;

import static org.junit.Assert.assertEquals;
import static org.powermock.api.mockito.PowerMockito.mockStatic;
import static org.powermock.api.mockito.PowerMockito.when;

import org.junit.Test;
import org.junit.runner.RunWith;
import org.powermock.core.classloader.annotations.PrepareForTest;
import org.powermock.modules.junit4.PowerMockRunner;

final class FinalClassWithStaticCall {
  public static int getIntStatic() {
    return 1;
  }
}

@RunWith(PowerMockRunner.class)
@PrepareForTest(FinalClassWithStaticCall.class)
public class TestStaticMockingWithoutPowerMockRunner {
  @Test
  public void testStaticCall() {
    mockStatic(FinalClassWithStaticCall.class);
    when(FinalClassWithStaticCall.getIntStatic()).thenReturn(2);

    assertEquals(FinalClassWithStaticCall.getIntStatic(), 2);
  }
}

但是当切换到这样的规则时:

package com.test.powermockstatics;

import static org.junit.Assert.assertEquals;
import static org.powermock.api.mockito.PowerMockito.mockStatic;
import static org.powermock.api.mockito.PowerMockito.when;

import org.junit.Rule;
import org.junit.Test;
import org.powermock.core.classloader.annotations.PrepareForTest;
import org.powermock.modules.agent.PowerMockAgent;
import org.powermock.modules.junit4.rule.PowerMockRule;

final class FinalClassWithStaticCall {
  public static int getIntStatic() {
    return 1;
  }
}

@PrepareForTest(FinalClassWithStaticCall.class)
public class TestStaticMockingWithoutPowerMockRunner {
  static {
    PowerMockAgent.initializeIfNeeded();
  }

  @Rule
  public PowerMockRule rule = new PowerMockRule();

  @Test
  public void testStaticCall() {
    mockStatic(FinalClassWithStaticCall.class);
    when(FinalClassWithStaticCall.getIntStatic()).thenReturn(2);

    assertEquals(FinalClassWithStaticCall.getIntStatic(), 2);
  }
}

我得到以下异常:

java.lang.IllegalArgumentException异常:在org.mockito.cglib.proxy.Enhancer.generateClass(Enhancer.java:447)在org.mockito.cglib.core.DefaultGeneratorStrategy.generate不能继承final类类com.test.powermockstatics.FinalClassWithStaticCall( DefaultGeneratorStrategy.java:25)在org.mockito.cglib.core.AbstractClassGenerator.create(AbstractClassGenerator.java:217)在org.mockito.cglib.proxy.Enhancer.createHelper(Enhancer.java:378)在org.mockito.cglib .proxy.Enhancer.createClass(Enhancer.java:318)在org.mockito.internal.creation.jmock.ClassImposterizer.createProxyClass(ClassImposterizer.java:110)在org.mockito.internal.creation.jmock.ClassImposterizer.imposterise(ClassImposterizer的.java:62)在org.powermock.api.mockito.internal.mockcreation.MockCreator.createMethodInvocationControl(MockCreator.java:111)在org.powermock.api.mockito.internal.mockcreation.MockCreator.mock(MockCreator.java:60 )在com.test.pow的org.powermock.api.mockito.PowerMockito.mockStatic(PowerMockito.java:70)ermockstatics.TestStaticMockingWithoutPowerMockRunner.testStaticCall(TestStaticMockingWithoutPowerMockRunner.java:30)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.的java:43)在java.lang.reflect.Method.invoke(Method.java:606)在org.junit.runners.model.FrameworkMethod $ 1.runReflectiveCall(FrameworkMethod.java:47)在org.junit.internal.runners. model.ReflectiveCallable.run(ReflectiveCallable.java:12)在org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)在org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java: 17)在org.powermock.modules.junit4.rule.PowerMockStatement.evaluate(PowerMockRule.java:49)在org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)在org.junit.runners.BlockJUnit4ClassRunner.runChild (BlockJUnit4ClassRunner.java:70)在org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)在org.junit.runners.ParentRunner $ 3.run(ParentRunner.java:238)在org.junit.runners.ParentRunner $ 1.schedule(ParentRunner.java:63)在组织.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)在org.junit.runners.ParentRunner.access $ 000(ParentRunner.java:53)在org.junit.runners.ParentRunner $ 2.evaluate(ParentRunner.java:229 )在org.junit.runners.ParentRunner.run(ParentRunner.java:309)在org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)在org.eclipse.jdt.internal. junit.runner.TestExecution.run(TestExecution.java:38)在org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)在org.eclipse.jdt.internal.junit.runner. RemoteTestRunner.runTests(RemoteTestRunner.java:683)在org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)在org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main( RemoteTestRunner 的.java:197)

我遵循文档的建议:

在类路径中将junm之前的powermock-module-junit4-rule-agent放入

如果这是PowerMock中的错误或期望的行为(即,你根本无法使用a 模拟static一个final类的方法),有没有人知道官方单词PowerMockRule？

编辑:

请参阅GáborLipták的回答中的澄清细节.我不希望使用静态加载代理,因为它出现在动态加载代理应该能够完成工作的？

我知道静态启动代理会起作用.(不幸的是,这不是我项目中的一个选项.)所以有人知道动态加载的Agent的失败是否是PowerMock中的错误？或者一个已知的限制; 为什么？

Answer 1

你需要准备课程进行测试!

@PrepareForTest(MyFinalClass.class)

Answer 2

对于模拟最终类，类路径是不够的。您需要 JVM 代理。

根据文档：

在某些情况下（例如模拟最终类），可能需要在 Maven 中急切地加载 PowerMock 代理，以便测试在 Surefire 中运行。如果您遇到这种情况，请将以下内容添加到您的 pom.xml 中：

需要 JVM 参数来模拟最终类：

-javaagent:${settings.localRepository}/org/powermock/powermock-module-javaagent/1.5.6/powermock-module-javaagent-1.5.6.jar