How to make gradle not to mark build failed if no tests are found

Question

As the title says, how can I make gradle not to fail a test task if no tests are found? I ran into this problem when I was using the --tests command line option with a multi-subproject project. For instance, this command below will run all tests in class FooTest from subproject A:
gradle test --tests com.foo.bar.FooTest

However, this command fails because of something like this:

Execution failed for task ':B:test'.
> No tests found for given includes: [com.foo.bar.FooTest]

BTW, I know something like below will succeed. But is it possible to make it succeed even with the test task? It's kind of annoying to type a test task name longer than test.

gradle :A:test --tests com.foo.bar.FooTest

Answer 1

The behavior you described is the current Gradle behavior, there is already a ticket on Gradle forum, see https://discuss.gradle.org/t/multi-module-build-fails-with-tests-filter/25835

Based on the solution described in this ticket, you can do something like that to disable the 'failIfNoTest' default behavior:

In your root project build (or better: in an InitScript in your Gradle USER_HOME dir, to make this behavior available for all your local projects)

gradle.projectsEvaluated {
    subprojects {
        // TODO: filter projects that does not have test task...
        test {
            filter {
                setFailOnNoMatchingTests(false)
            }
        }
    }
}

Then you can execute the following command without having errors if the given test doesn't exist in all sub-projects:

gradle test --tests com.foo.bar.FooTest