Leonard Brünings
Leonard Brünings
I'd like to avoid having to do a full dependency tree calculation for each test, for global extensions this is so much of an issue, but annotation based ones can...
The relevant logic in `MockitoPostProcessor` was added after I did the implementation for Spock based on it.
It is not a bug, but maybe it should be mentioned somewhere. Mocks are always bound to a `Specification` instance and should not be shared. The `setupSpec` runs in a...
GroovyMocks work via modification of the meta-class. Using static compilation will basically turn groovy bytecode into java equivalent bytecode, e.g. static binding and thus no meta-class magic.
@timic yes, I don't think there is anything we can do about it. The bytecode generated for `StaticService` is the same whether `FinalClass` is indeed `final` or not, it uses...
You actually get an instance of the mock when you call ` Step mock = GroovyMock(Step, global: true)`. And the contract for `Mock` is that you have to define *every*...
It is all a matter of priority and resources, and as this is an issue that doesn't affect many users it isn't that high on my list, that doesn't mean...
Hi @jff, thanks for implementing this feature. When changing something on the spock-core language level, we have to ask ourselves, does this new feature improve the readability/clarity of the test...
Another problem we have, is that using `>>> [{ code }]` is currently the only easy way to actually return a closure. Which makes this a breaking change. As a...