spock | A GUI frontend for Grunt | DevOps library

Put your method call into a closure and evaluate the closure during each iteration:

As you mention, I believe this is a consequence of the upgrade to Groovy 3. A quick look shows that DefaultGroovyMethods leftShift(OutputStream self, InputStream in) was previously marked as deprecated and it appears as though it was removed during 3.0's changes (though I can't find exactly where). However, you can still find the same method in IOGroovyMethods.

Your issue is that the RESTClient/HttpBuilder library has not been updated to reflect Groovy's changes. However, you can easily extend the RESTClient and provide an override for the defaultSuccessHandler method, pointing the handler to the correct location:

A type declaration like

I am not familiar with the testing framework you mentioned but this is most likely not a framework problem. You are passing primitives arguments.

As stated in the docs

Primitive arguments, such as an int or a double, are passed into methods by value. This means that any changes to the values of the parameters exist only within the scope of the method. When the method returns, the parameters are gone and any changes to them are lost.

I cloned your project and noticed a few outdated things (Groovy, Spock and GMaven+ versions). Upgrading them did not change the outcome, I can still reproduce your problem.

A also noticed that in your two branches the POM differs in more than just the Karate version number, also the dependencies differ. If I use the ones from the 1.0.1 branch, tests do not work under 0.9.5 anymore. So I forked your project and sent you two pull requests for each branch with a dependency setup working identically for both Karate versions. Now the branches really just differ in the Karate version number:

https://github.com/kriegaex/spock-karate-example/compare/karate-0.9.5...kriegaex:karate-1.0.1

BTW, for some reason I had to compile your code running JDK 11, JDK 16 did not work. GMaven+ complained about Java 16 groovy class files (bytecode version 60.0), even though GMaven+ should have used target level 11. No idea what this is about. Anyway, on Java 11 I can reproduce your problem. As the Spock version is identical for both branches, I guess the problem is within Karate itself. I recommend to open an issue there, linking to your GitHub project (after you have accepted my PRs). Spock definitely sets the system property, I have added more log output into the stubbing closure order to verify that. Maybe this is an issue concerning how and when Karate communicates with Spock.

Update: Peter Thomas suggested in his answer to store the value to be transferred to the feature in a Java object and access that one from the feature after the Spock test has set it. I guess, he means something like this:

https://github.com/kriegaex/spock-karate-example/commit/ca88e3da

You are sufferring from object slicing, both in your return type from from_str and in your vector .

Like it or not, you are going to have to use pointers, but if you use smart pointers then the pain will go away. So, first change your from_str function like so:

@Category is a junit4 feature, Spock 2.0 is a proper TestEngine on the JUnit Platform, take a look at Include and Exclude of the Spock docs. Hint: it is a groovy file so you can add logic if you need any.

Spock cannot mock final classes and/or methods and CsvParser as well as stopParsing() are final. You can try using the spock mockable extension to make those classes/methods non-final.

Spock relies heavily on AST-Transformations, for that it is necessary that certain constructs are used.

1 * service.doSomething() >> x will just return x

1 * service.doSomething() >> { x } will run the code in the closure and return x

So, if you want to delay the execution of the response code, but still want to put it in a variable you need to wrap the execution in a closure.