Alexander Kriegisch

For most things you said my template answer for the time being is: You are probably right. I was kinda busy lately, so I have not done anything with Sarek...

> I personally would actually prefer the explicit flag, same as `global: true` this indicates I'm doing something to work around a design flaw and shouldn't just happen. I guess...

I still found no explanation and also no workaround with `mockStatic` which I could later check interactions (number of calls) on with `verifyStatic`, but I did find a simple workaround...

> I assume the problem is related to Groovy code transformations taking place in Spock tests or maybe something about delegates, meta classes or how methods are discovered and called...

Thanks for the good explanation and for confirming my educated guesses. Besides, the existing tickets to support mocking for static methods and final classes/methods in Spock for non-Groovy code would...

Dear Björn, the following rant is not directed personally at you and I don't think that you are one of the Spock maintainers (feel free to correct me if I...

Far from wishing to interfere with internal processes in the group of developers, please bear with me when I am asking if you guys think you could conclude the review...

Oh, I see. Thanks for the update. 😀

I did not clone your repo yet, just glanced at the Maven config and the log output. Some thoughts: * Surefire and Failsafe run in two completely different Maven phases...

> the issue is that during the surefire phase there were no test classes for Spock to collect. During Sputnik times, global extensions were run only if there were actual...