Marcin Zajączkowski

I see it useful in all those cases where `assert` is required in Spock. Mostly assertions extracted to a separate methods (for reusability) or assertions done inside a closure. There...

I ran into that problem again today with the integration tests in my Gradle plugin: ``` expect: verifyAll { PIT_PARAMETERS_NAMES_NOT_SET_BY_DEFAULT.each { assert !result.standardOutput.contains("${it}=") } } ``` It's hard to leave...

Created an issue in Groovy: https://issues.apache.org/jira/browse/GROOVY-9369 . Paul K. declared to take a look at that in the Groovy 4 development.

Spock 1.3 should provide asm7 (build.gradle): > asm: "org.ow2.asm:asm:7.0", Are you sure that nothing else causes asm4 on your classpath?

I missed that it was about "passing Opcode of ASM4", not that asm:4 was used.

This PR looks like a building block for some bigger task (like externalization of data providers). It would be probably good to describe (at least in the PR itself description...

You could use a mechanism usually used in `Spy()` to instruct Spock to call a real method on the underlying object. ```groovy given: Foo foo = Mock() foo.doThingDefault(_) >> {...

`Optional.empty()` is used by default only for stubs, not mocks. @chrylis Could you send a complete specification (a test class) that reproduce the problem? Does that particular example work in...

Even better you can use version 0.4.3: 'io.codearte.jfairy:jfairy:0.4.3' Btw, the easy way to check what to paste to get it into Gradle/Maven/whatever is to click the Maven Central badge in...

I've been debugging it years ago and after the code analysis it was problematic for Spock to determine that `def` is in fact the `PollingConditions` type. Maybe it will be...