Spock test method names appear as "$spock_feature_<number>_<number>" when running tests with PaxExam runner
Hello. I am using Spock in conjunction with pax-exam to test bundle deployment and functionality in a custom karaf distribution. When I run the tests, it refers to tests by what appears to be an uninterpreted variable name. An example is "$spock_feature_1_0". Am I doing something wrong, or is this a effect of using spock with the PaxExam (or other junit) runner?
Here is how my integration test project is set up:
I have a parent class called TestSupport which I have adapted from KarafTestSupport.java
by converting it to Groovy and removing some of the methods and
properties that I do not currently need in my tests. This class extends
Specification, but it does not implement any Spock tests. Its purpose
is to set up the Karaf container in preparation for the tests, implement
common behavior for the tests, and to provide an (indirect) extension
of the Specification class for the test classes.
Here is an abbreviated example of one of my test classes:
It definitely feels clunky to have to make the method signatures look so un-groovy, but the PaxExam runner does not run the tests if they are not annotated with @Test, and if they are not declared as "public void".
Does anyone have any ideas about why the test methods are displayed as "$spock_feature_1_0" or what I might be able to do better in combining Spock with PaxExam? Thanks in advance!