带有闭包的 Spock 单元测试以错误“没有可运行的方法”结束

Question

I wrote a simple feature method with the following then block :

then:
1 * view.setAttachments({ it?.size == 3 })

But the gradle test fails with the error :

initializationError

java.lang.Exception: No runnable methods
    at org.junit.runners.BlockJUnit4ClassRunner.validateInstanceMethods(BlockJUnit4ClassRunner.java:169)
    at org.junit.runners.BlockJUnit4ClassRunner.collectInitializationErrors(BlockJUnit4ClassRunner.java:104)
    at org.junit.runners.ParentRunner.validate(ParentRunner.java:355)
    ...

initializationError

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)
    ...

I noticed that if I remove the closure, there is no more error

then:
1 * view.setAttachments(_) // everything works well without closure!

It seems Spock tries to run the closure like it was another test method... How to avoid that ?

Answer 1

I had a similar problem trying to write a spring-boot test.

Do not use @RunWith(SpringRunner.class) and try removing your junit runner if you're using another one.

For me my Spock Specification executed properly without specifying the SpringRunner.

Answer 2

I found that the issue in my case is that the test file/class ended with Test , rather than Spec . Changing that resolved the issue (eg SomeServiceTest -> SomeServiceSpec ).

Answer 3

I had the same problem. For me worked moving the test file from "src" directory to "Test" directory.

Answer 4

Try adding the following property to your build.gradle

 test {
        systemProperty 'project.buildDir', project.buildDir
    }