UX: improve error message when test is filtered out

[melix]

Context

This caused me a headache which has hopefully been mitigated thanks to the help of @rieske . Basically, if a test task is configured to filter out tests:

    register<SmokeTest>("smokeTest") {
        description = "Runs Smoke tests"
        configureForSmokeTest(*santaProjects)
        useJUnitPlatform {
            filter {
                excludeTestsMatching(gradleBuildTestPattern)
            }
        }
    }

and that you run via CLI, or in my case, via the IDE, this test task, you get this error message:

> No tests found for given includes: [org.gradle.smoketests.GradleBuildConfigurationCacheSmokeTest](filter.includeTestsMatching)

which is not quite correct: tests were found, but they were filtered out. So it's not a bug in the engine not finding the test, it's actually that I was calling the wrong task.

Suggestion:

> No tests were executed for given includes: [org.gradle.smoketests.GradleBuildConfigurationCacheSmokeTest](filter.includeTestsMatching) but the following tests were found and ignored by a filter on the task configuration:
   - org.gradle.smoketests.GradleBuildConfigurationCacheSmokeTest

[ldaley]

The experience is similar when using --tests. The feedback is close to incomprehensible.

[melix]

Yes, this is the very same issue: when you run a test from IDEA like I did, it actually uses --tests and the fact Gradle tells you that the test you just started doesn't exist is... frustrating.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution.

[melix]

ping

[sschuberth]

Actually, I believe the "No tests found for given includes" message is fine. It all boils down to who you think "found" refers to: To the test engine, or to Gradle. To me it refers to Gradle, as the message comes from Gradle. So Gradle did not "find" the test (because it was filtered), but the test engine did find it.

Anyway, what I believe is more confusing than that is that the message talks about "includes" although only an exclude was defined. Maybe better use a wording like "No tests to execute remaining after filtering".

[lingocoder]

…The experience is similar when using --tests. The feedback is close to incomprehensible…

Can confirm :(