I've had a quick look at this. The test runs fine, however the Cucumber JUnit runner notifies JUnit/Gradle in an uncommon way (that seems to be outside the spec) and Gradle doesn't seem to like this. If the behavior of the Cucumber runner is deemed acceptable, we could support this in a future version of Gradle.
-- Peter Niederwieser Principal Engineer, Gradleware http://gradleware.com Creator, Spock Framework http://spockframework.org Twitter: @pniederw -- View this message in context: http://gradle.1045684.n5.nabble.com/JUnit-Tests-not-running-the-same-way-tp5519457p5520081.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
