gpt4 book ai didi

java - 具有本地内部类的 JUnit 4 测试方法在测试用例之间不一致

转载 作者:行者123 更新时间:2023-11-30 10:42:01 24 4
gpt4 key购买 nike

好吧,我尽我所能搜索了这个但找不到任何东西。我是第一次提问所以要温柔。 :p

在一个测试用例中,我有一个测试方法来测试给定事件监听器方法是否被触发。

public class TestCaseDoingSupport {

public TestCaseDoingSupport() {
super();
}
@Test
public void testFireEventDoingSomething() {

class LocalDoingListener extends DoingAdapter {

public LocalDoingListener() {
super();
}
public void onStartedDoingSomething(DoingEvent event) {
Assert.assertEquals(DoingClass.STARTED_DOING_SOMETHING, event.getDoingStatus());
}
}

DoingListener listener = new LocalDoingListener();
DoingSupport support = new DoingSupport(new DoingClass());
support.addDoingListener(listener);
support.fireStartedDoingSomething();
}
}

我遇到的问题是:这个 exact 模式用于另外两个事件监听器的另外两个测试用例(在同一个项目中)并且它工作得很好,但在我的测试用例中有问题我得到(从测试报告)java.lang.Exception: Test class should have exactly one public constructor.

我真的不明白为什么这种模式在一个测试用例中有效,但在另一个测试用例中却无效——我什至尝试去掉构造函数,但没有任何区别。有没有人遇到过这个问题,如果有,您是如何解决的?

非常感谢。

编辑:我尝试公开方法局部类的构造函数(反射(reflect)在发布的代码片段中),但测试报告中的投诉相同。在命令行中,gradle 报告:

com.example.testTestCaseDoingSupport$1LocalDoingListener > initializationError FAILED
java.lang.Exception

下面发布了完整的堆栈跟踪。

java.lang.Exception: Test class should have exactly one public zero-argument constructor
at org.junit.runners.BlockJUnit4ClassRunner.validateZeroArgConstructor(BlockJUnit4ClassRunner.java:147)
at org.junit.runners.BlockJUnit4ClassRunner.validateConstructor(BlockJUnit4ClassRunner.java:124)
at org.junit.runners.BlockJUnit4ClassRunner.collectInitializationErrors(BlockJUnit4ClassRunner.java:103)
at org.junit.runners.ParentRunner.validate(ParentRunner.java:355)
at org.junit.runners.ParentRunner.<init>(ParentRunner.java:76)
at org.junit.runners.BlockJUnit4ClassRunner.<init>(BlockJUnit4ClassRunner.java:57)
at org.junit.internal.builders.JUnit4Builder.runnerForClass(JUnit4Builder.java:10)
at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)
at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:26)
at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)
at org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:26)
at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:84)
at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
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.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
at org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
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.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
at org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

最佳答案

好的,我找到了。在我的 gradle 脚本中,我有这个

tasks.withType(Test) {
scanForTestClasses = false
exclude "**/*\$5*.class"
}

避免将内部类视为测试类。将其编辑为 exclude "**/*\$*.class" 解决了 所有 内部类。

我不敢相信我之前没有看到这个......

关于java - 具有本地内部类的 JUnit 4 测试方法在测试用例之间不一致,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/38294404/

24 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com