How do I run all the tests in a gradle multi-module project? So far, I need to run each module's tests seperately, I can't just run gradlew test...

You should be able to run

./gradlew :<module-name>:test

to just run the tests in one module.

Yeah, that's what I'm currently doing, but I need to run the whole suite in the CI, or after making major changes...

just do

./gradlew check

or

/.gradlew test

at the top level

Tried, didn't work...

what's the error

Test events not received

sounds like you don't have the test task configured at your project root

I have this at the root:

plugins {
    kotlin("jvm")
    kotlin("kapt")
    id("com.squareup.anvil")
}

Drop this in your root module

allprojects {
  afterEvaluate {
    tasks {
        if (tasks.findByName("test") == null) {
          register("test") {
            dependsOn(withType(KotlinTest::class))
            group = "verification"
        }
      }
    }
  }
}

That's only if you're using the kotest gradle plugin right ?

kotest gradle plugin?

Oh never mind, I see, @Big Chungus means you don't need to use

check

task.

KotlinTest::class

or

KoTest::class

? And @sam, that does the same as what he posted?

no, we're giving different options I think

Yes, kotest != gradle

build.gradle.kts:78:23: Unresolved reference: findByName ...

How's this

allprojects {
    afterEvaluate {
        tasks {
            if (findByName("test") == null) {
                register("test") {
                    dependsOn(withType(KotlinTest::class))
                    group = "verification"
                }
            }
        }
    }
}

@sam I copied this from hoplite:

tasks.named<Test>("test") {
    useJUnitPlatform()
    testLogging {
        showExceptions = true
        showStandardStreams = true
        exceptionFormat = FULL
    }
}

and some tests started running, there's a few compile errors now, but it seems like it's running. Thanks to both of you for pointing out the right direction!

you were probably missing the useJUnitPlatform() at the top level then

A while passed since I tried this... I'm still having these problems. Only my domain module's tests are being run... I really wonder what could be wrong...?