Filtering by tags prevents Spock specs from being executed.

[jakub-bochenski]

Neither Spock 1.x nor Spock 2.x support tags, so they should not be affected by a tag filter. Yet it seems they are

Steps to reproduce

Update: I was able to spot this in the debugger (somehow the debug output is not printed even when I run gradle with -d)

I think this clearly shows there is a bug. Tags should not affect other engines than Jupiter.

--

Add some Spock 1.x Specs and have a gradle test task configured as follows:

    test {
            useJUnitPlatform {
                includeTags("SomeTag")
                includeEngines("junit-vintage")
            }
    }

Observe specs are not being executed.
If you comment out the line with "includeTags" the specs are executed.

I've checked in the debugger that a RunnerTestDescriptor with a Sputnik runner is being discovered (the Specs are not being skipped/ignored by Spock).

The same happens with Spock 2.x

    test {
            useJUnitPlatform {
                includeTags("SomeTag")
                excludeEngines("junit-vintage")
            }
    }

Context

• Used versions (Jupiter/Vintage/Platform): 5.6.3 / 1.6.3
• Build Tool/IDE: gradle 6.8.3
• Spock 1.3-groovy-2.5, 2.0-M2-groovy-2.5

[marcphilipp]

As explained in spockframework/spock#1288 (comment), this works as designed.