Renato Athaydes

This is a good idea... I will look into adding this feature.

Oh, thanks for reporting! Will have a look into it.

Spock is not reporting that the feature was not executed. It doesn't seem to give any information at all indicating that the test did not run. I will continue trying...

As far as I can tell, it is currently impossible to know that the test did not execute. Spock code calls only `org.junit.runner.notification.RunNotifier#fireTestAssumptionFailed` but there's no way I can see...

The problematic code is in `org.spockframework.runtime.JUnitSupervisor`: ```java if (exception instanceof AssumptionViolatedException) { // Spock has no concept of "violated assumption", so we don't notify Spock listeners // do notify JUnit...

I would make a pull request against Spock to make sure it does what @yeugenius suggested, but I am very short on spare time right now... hope someone else can...

I've come up with a workaround for this issue. I added a new extension function to `Specification` so that instead of explicitly throwing an `AssumptionViolatedException` from your tests, you can...

Ah, nevermind, spock-reports is just a report creator... I don't want to introduce unrelated APIs. My next best suggestion is to capture invocations of the `AssumptionViolatedException` constructor and assume that...

The tools that work, only work because they integrate with JUnit, not directly with Spock. spock-reports integrates directly with Spock, not with JUnit, and because Spock does not notify spec...

I thought of submitting a PR doing this, but it was not clear to me how to handle test iterations. Your change seems incorrect for two reasons: * you would...