【发布时间】:2014-10-01 17:26:24
【问题描述】:
我正在使用 PowerMock 来验证 Gradle 任务中对 JavaCC 的静态调用。
在我的 @Before 注释方法中(我正在使用 JUnit4 和 Mockito,顺便说一句),我有这个:
Project project = ProjectBuilder.builder().build();
当我在这个类中运行任何带有注释的测试用例时
@RunWith(PowerMockRunner.class)
我得到以下信息:
java.lang.NoClassDefFoundError: Could not initialize class org.gradle.testfixtures.internal.ProjectBuilderImpl
at org.gradle.testfixtures.ProjectBuilder.<init>(ProjectBuilder.java:46)
at org.gradle.testfixtures.ProjectBuilder.builder(ProjectBuilder.java:54)
at ca.coglinc.gradle.plugins.javacc.CompileJavaccTaskTest.setUp(CompileJavaccTaskTest.java:43)
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.internal.runners.MethodRoadie.runBefores(MethodRoadie.java:132)
at org.junit.internal.runners.MethodRoadie.runBeforesThenTestThenAfters(MethodRoadie.java:95)
at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl$PowerMockJUnit44MethodRunner.executeTest(PowerMockJUnit44RunnerDelegateImpl.java:294)
at org.powermock.modules.junit4.internal.impl.PowerMockJUnit47RunnerDelegateImpl$PowerMockJUnit47MethodRunner.executeTestInSuper(PowerMockJUnit47RunnerDelegateImpl.java:127)
at org.powermock.modules.junit4.internal.impl.PowerMockJUnit47RunnerDelegateImpl$PowerMockJUnit47MethodRunner.executeTest(PowerMockJUnit47RunnerDelegateImpl.java:82)
at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl$PowerMockJUnit44MethodRunner.runBeforesThenTestThenAfters(PowerMockJUnit44RunnerDelegateImpl.java:282)
at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:86)
at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:49)
at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.invokeTestMethod(PowerMockJUnit44RunnerDelegateImpl.java:207)
at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.runMethods(PowerMockJUnit44RunnerDelegateImpl.java:146)
at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl$1.run(PowerMockJUnit44RunnerDelegateImpl.java:120)
at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:33)
at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:45)
at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.run(PowerMockJUnit44RunnerDelegateImpl.java:122)
at org.powermock.modules.junit4.common.internal.impl.JUnit4TestSuiteChunkerImpl.run(JUnit4TestSuiteChunkerImpl.java:104)
at org.powermock.modules.junit4.common.internal.impl.AbstractCommonPowerMockRunner.run(AbstractCommonPowerMockRunner.java:53)
at org.powermock.modules.junit4.PowerMockRunner.run(PowerMockRunner.java:53)
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)
我想我的测试类路径中缺少 Gradle 运行时配置,但找不到解决方法。删除 PowerMockRunner,我的测试运行正常,但是我不能有一个依赖于 PowerMock 的测试(我知道不需要 PowerMock 的东西应该是可测试的,但我不是在写 JavaCC 并且仍然想验证它是否被调用了一些参数)。有什么想法吗?
【问题讨论】:
-
如果仅用于测试您应该在
dependencies块中添加testCompile gradleApi()。 -
我已经有了
compile gradleApi(),据我了解,它还将包含在 testCompile 和 testRuntime 配置下。这有效的证明是我的测试编译得很好。但是,我尝试了以防万一,但仍然失败并出现同样的错误。 -
还有一件事我不明白:当我运行
gradle dependencies时,gradleApi 依赖项在任何配置下都不会出现。 -
是的
compile也被添加到test*。不知道为什么gradleApi()在运行gradle dependencies时不显示。它应该是。您在网络上的某个地方有 SSCCE 吗? -
是的,请参阅 github.com/johnmartel/javaccPlugin 并运行
./gradlew clean :javacc-gradle-plugin:test您会收到错误消息。我在我的测试类路径中添加了 javassist 和 objenesis,我在 ProjectBuilderImpl 的初始化中得到了稍微更精确的堆栈跟踪,但结果是一样的。