The older G4NB plugin had smarts or something such that it looked at pathing of where a test file was and adjusted the gradle invocation accordingly.
So for example, a Spock spec in: src/test/groovy/com/blah/blah/SomeSpec.groovy would invoke gradle a bit like like: ./gradlew tests --tests com.blah.blah.SomeSpec And if the Spock spec was here: src/integrationTest/groovy/com/blah/blah/OtherSpec.groovy would invoke gradle a bit like like: ./gradlew integrationTest --tests com.blah.blah.OtherSpec Basically, it seemed to do some simple matching of the path against tasks in the build file and away it went. Can the 11.3, using builtin gradle support support this kind of behavior? If so how?
