Leonard Brünings
Leonard Brünings
@szpak I was thinking about adding new `withContext`/(`verifyAllContext`|`verifyAllWithContext`)? methods, that would just add the `target` object to the exception message.
A simple workaround is to still use `it.contains("bar")`
Rule support is made on a best-effort basis, as they don't perfectly match with Spocks concepts, but works well enough most of the time. However, there might be cases -...
Hi, thanks for your contribution. However, I don't think that this will be a good fit for spock(-core). * Spock does nothing with this annotation, so by itself it is...
Could you also check if there are other relevant new additions that were made to `MockitoPostProcessor` that are missing in `SpockMockPostProcessor`?
IMHO releases should be tagged as well as being reproducible, which requires that the version information is updated in SCM be it build.gradle or gradle.properties. So instead of having a...
I'm going to close this, the release is semi automated which is fine for a project like Spock IMHO.
I'd prefer a separate artifact. Do you expect much change to those classes, I assumed that they are quite mature?
You are right @kemuri-9 I've also been thinking of having only the store in the core, as this can't really be emulated via extensions. The `ExtensionContext` can then be implemented...
@raphw what are your thoughts about this? How difficult would it be to add this to Spock?