Leonard Brünings

The greatest issue I see is with the rewrites performed by Spock for its mock handling. ```java class Spec extends spock.lang.Specification { def "simple Test"() { given: "a simple list"...

Yes the feature request is still on the radar, this PR will not be the basis for it though (reasons listed above). Unfortunately, we can't transform it into an issue,...

The contract of `Comparable` is that if the result of `compareTo` is `0` then `equals` should also be `true` and vice-versa. Spocks logic for a [plain argument](https://spockframework.org/spock/docs/1.3/all_in_one.html#_argument_constraints) is to use...

> Anyway, in Spock's current form, Mocks of Comparables do not meet the requirement you're describing Yes, mocks don't really adhere to any contract unless you tell them to. You...

I checked the documentation and I think it already [clearly states](https://spockframework.org/spock/docs/2.0/all_in_one.html#_equality_constraint): > The equality constraint uses groovy equality to check the argument, i.e, argument == constraint. We could add a...

@huehnerlady sorry for the late answer. We are working on spock-2.0 at the moment, so please wait for contributions until that branch is merged to master, otherwise it will create...

@huehnerlady > Keep in mind that this is how junit works as well. JUnit does not provide any mocking functionality that I know of. Did you mean Mockito? > When...

I agree with @robfletcher. This kind of grouping often leads to huge and hard to understand specs, simply because instead of using inheritance we just put everything related to `Foo`...

Hi, JUnit controls how Specs are executed, Spock only controls execution in a Spec. That means that Spock does not have an awareness of suites or other things like that....

Interactions are transformed at compile time and each argument is translated to its _own_ method call, e.g., `addEqualArg`. That is why this doesn't work at the moment, since it would...