Closed kriegaex closed 8 years ago
Thanks for the detailed report :) Seems that I am going to have plenty of work to do during Christmas, not only eating and spending time with family.
I will try hard to wrap all of it up before new year!
The road to hell is paved with good intentions, they say... ;-)
That was quite heavy joke ;)
If you have ever tried to renounce chocolate or start doing more sports, you know what I mean.
Sure, or reduce beer etc.
In general New Years resolutions ;)
I just found out by means of Maven Enforcer Plugin that conflicting JUnit versions from a BOM and our own project were the source of the problem. Somehow the shrink-wrapped WAR did not find the right version. Pinning down the version in the <dependencyManagement>
section of our root POM fixed our integration tests.
Sorry for the noise. This one was really nasty to debug. Now there is a little more time for you to celebrate Xmas (or to solve our other open tickets).
In order to log feature method names ("test method names") I added this JUnit rule to our code base:
I made all our unit tests inherit from
OurSpockSpec
and everything runs just fine.Now I did a similar thing for our Geb Tests which are executed in a WildFly server via Arquillian Spock Runner:
Now our Geb tests inherit from
OurGebSpec
(which they have done before anyway because other common methods are defined there) and the tests run fine locally from IntelliJ IDEA as well as Maven. But the very same Maven tests fail on our Jenkins integration server with the following error:As you can see, the method logging for this failing test as such works as can be seen at the very beginning of the log:
But then we have this problem (Spock 0.7-groovy-2.0, Groovy 2.4.1, by the way):
Any ideas?