did the thing where if you have no tests at all gradle test will error make it into gradle 9? wondering if I can delete my custom code that did that

Just tested with 9.0.0:

Execution failed for task ':test'.

> There are test sources present and no filters are applied, but the test task did not discover any tests to execute. This is likely due to a misconfiguration. Please check your test configuration. If this is not a misconfiguration, this error can be disabled by setting the 'failOnNoDiscoveredTests' property to false.

sweet, finally some code reduction 😛

If you have no test sources at all, it will not fail though, but be skipped for

NO-SOURCE

well.. progress is ... uh, progress?

I don't think that this will (or should) change. A task with no sources is skipped, this is just consistent.

I disagree vehemently 😉

If you use

--tests

or similar filtering and no test is found it also fails

other build systems are sane

But if there are no source files, there are no source files. The failure on not found tests is for capturing misconfigurations like having source files for one test engine but only execution other test engines which most probable is a configuration error, or telling to execute X while there is no X.

maybe tasks in general should fail if they need inputs and have none

They do

no source files should mean a task fails 😉

And the Test task is configured as

@SkipWhenEmpty

if there are no files to test

then that should be removed 😉

No it should not

disagree vehemently 😉

Just don't expect it to be accepted 🙂

I don't ever expect anything to be accepted

Don't use Gradle if you are that unhappy with it, but use one of the build tools you consider "sane" 🙂

ther aren't any sane build tools in java 😉

Btw. you can simply do

maybe tasks in general should fail if they need inputs and have none

using

tasks.configureEach {
    inputs.file(buildFile).skipWhenEmpty()
}

because a task is only skipped for

NO-SOURCE

if all

@SkipWhenEmpty

inputs are empty.

I have some kind of logic around this now... but I'll see if that's improved later

Of course my snippet only works if the

buildFile

actually exists

heh

To not depend on the build script file to exist, you could instead do

tasks.configureEach {
    val fakeFke = Files.createTempFile("fake", ".fke")
    fakeFke.toFile().deleteOnExit()
    inputs.file(fakeFke).skipWhenEmpty()
}

for example

I'll figure out how to keep this stuff up later

val available =
  tasks.register("tests available") {
    val java: Provider<FileCollection> = sourceSets.test.map { it.java }
    doLast {
      if (java.get().isEmpty) throw RuntimeException("no tests found")
    }
  }

inputs.dir(rootProject.file("buildSrc/src/main"))
  finalizedBy(available)

  afterSuite(
    KotlinClosure2<TestDescriptor, TestResult, Unit>(
      { descriptor, result ->
        if (descriptor.parent == null) {
          logger.lifecycle("Tests run: ${result.testCount}, Failures: ${result.failedTestCount}, Skipped: ${result.skippedTestCount}")
          if (result.testCount == 0L) throw IllegalStateException("You cannot have 0 tests")
        }
        Unit
      },
    ),
  )

I'll figure out how to keep this stuff up later

Uhm, didn't I just tell you how?

yeah, but I have to do it accross 5 projects that aren't building 😉