I’m getting `No tests found for given includes` wh...

# kotest

[bbaldino]

I’m getting No tests found for given includes when trying to run a single kotest test inside a gradle project--I assume this must be something dumb I’m missing but after googling around a bit I still haven’t seen anything that addresses it. I do have

tasks.withType<Test>().configureEach {
    useJUnitPlatform()
}

in build.gradle.kts

[bbaldino]

./gradlew tests -i doesn’t appear to run anything either (and intellij is set to use gradle to run tests).

[sam]

what deps do you have ?

[bbaldino]

io.kotest:kotest-runner-junit5:5.3.0

[sam]

that should be allyou need

[sam]

this a new project or just stopped working ?

[bbaldino]

this is a new project, just adding kotest

[sam]

what is tests -i ?

[sam]

./gradlew check will run all tests

[bbaldino]

test -i is: (big block incoming)

[bbaldino]

bbaldino@BBALDINO-M-8A1Z sessions % ./gradlew test -i
Initialized native services in: /Users/bbaldino/.gradle/native
Initialized jansi services in: /Users/bbaldino/.gradle/native
Removing 0 daemon stop events from registry
Starting a Gradle Daemon (subsequent builds will be faster)
Starting process 'Gradle build daemon'. Working directory: /Users/bbaldino/.gradle/daemon/7.3.3 Command: /usr/local/Cellar/openjdk@11/11.0.10/libexec/openjdk.jdk/Contents/Home/bin/java --add-opens java.base/java.util=ALL-UNNAMED --add-opens java.base/java.lang=ALL-UNNAMED --add-opens java.base/java.lang.invoke=ALL-UNNAMED --add-opens java.base/java.util=ALL-UNNAMED --add-opens java.prefs/java.util.prefs=ALL-UNNAMED --add-opens java.prefs/java.util.prefs=ALL-UNNAMED --add-opens java.base/java.nio.charset=ALL-UNNAMED --add-opens java.base/java.net=ALL-UNNAMED --add-opens java.base/java.util.concurrent.atomic=ALL-UNNAMED -XX:MaxMetaspaceSize=256m -XX:+HeapDumpOnOutOfMemoryError -Xms256m -Xmx512m -Dfile.encoding=UTF-8 -Duser.country=US -Duser.language=en -Duser.variant -cp /Users/bbaldino/.gradle/wrapper/dists/gradle-7.3.3-bin/6a41zxkdtcxs8rphpq6y0069z/gradle-7.3.3/lib/gradle-launcher-7.3.3.jar org.gradle.launcher.daemon.bootstrap.GradleDaemon 7.3.3
Successfully started process 'Gradle build daemon'
An attempt to start the daemon took 1.387 secs.
The client will now receive all logging from the daemon (pid: 68986). The daemon log file: /Users/bbaldino/.gradle/daemon/7.3.3/daemon-68986.out.log
Starting build in new daemon [memory: 512 MiB]
Using 8 worker leases.
Watching the file system is configured to be enabled if available
Now considering [/Users/bbaldino/work/sessions] as hierarchies to watch
File system watching is active
Starting Build
Skipping Kotlin DSL script compilation (Settings/TopLevel/stage1) as it is up-to-date.
Settings evaluated using settings file '/Users/bbaldino/work/sessions/settings.gradle.kts'.
Projects loaded. Root project using build file '/Users/bbaldino/work/sessions/build.gradle'.
Included projects: [root project 'sessions', project ':sessions-service']

> Configure project :
Evaluating root project 'sessions' using build file '/Users/bbaldino/work/sessions/build.gradle'.

> Configure project :sessions-service
Evaluating project ':sessions-service' using build file '/Users/bbaldino/work/sessions/sessions-service/build.gradle.kts'.
Caching disabled for Kotlin DSL plugin accessors for classpath '12d94f928b3a8d08ab323c90e05cf87b' because:
  Build cache is disabled
Skipping Kotlin DSL plugin accessors for classpath '12d94f928b3a8d08ab323c90e05cf87b' as it is up-to-date.
Caching disabled for Kotlin DSL script compilation (Project/TopLevel/stage1) because:
  Build cache is disabled
Skipping Kotlin DSL script compilation (Project/TopLevel/stage1) as it is up-to-date.
kotlin scripting plugin: created the scripting discovery configuration: kotlinScriptDef
kotlin scripting plugin: created the scripting discovery configuration: testKotlinScriptDef
Caching disabled for Kotlin DSL accessors for project ':sessions-service' because:
  Build cache is disabled
Skipping Kotlin DSL accessors for project ':sessions-service' as it is up-to-date.
Caching disabled for Kotlin DSL script compilation (Project/TopLevel/stage2) because:
  Build cache is disabled
Skipping Kotlin DSL script compilation (Project/TopLevel/stage2) as it is up-to-date.
All projects evaluated.
Selected primary task 'test' from project :
Tasks to be executed: [task ':sessions-service:compileKotlin', task ':sessions-service:compileJava', task ':sessions-service:processResources', task ':sessions-service:classes', task ':sessions-service:compileTestKotlin', task ':sessions-service:compileTestJava', task ':sessions-service:processTestResources', task ':sessions-service:testClasses', task ':sessions-service:test']
Tasks that were excluded: []
:sessions-service:compileKotlin (Thread[Execution worker for ':' Thread 4,5,main]) started.

> Task :sessions-service:compileKotlin UP-TO-DATE
Watching 1 directory hierarchies to track changes
Caching disabled for task ':sessions-service:compileKotlin' because:
  Build cache is disabled
Skipping task ':sessions-service:compileKotlin' as it is up-to-date.
:sessions-service:compileKotlin (Thread[Execution worker for ':' Thread 4,5,main]) completed. Took 0.646 secs.
:sessions-service:compileJava (Thread[Execution worker for ':' Thread 4,5,main]) started.

> Task :sessions-service:compileJava NO-SOURCE
file or directory '/Users/bbaldino/work/sessions/sessions-service/src/main/java', not found
Skipping task ':sessions-service:compileJava' as it has no source files and no previous output files.
:sessions-service:compileJava (Thread[Execution worker for ':' Thread 4,5,main]) completed. Took 0.003 secs.
:sessions-service:processResources (Thread[Execution worker for ':' Thread 4,5,main]) started.

> Task :sessions-service:processResources UP-TO-DATE
Caching disabled for task ':sessions-service:processResources' because:
  Build cache is disabled
Skipping task ':sessions-service:processResources' as it is up-to-date.
:sessions-service:processResources (Thread[Execution worker for ':' Thread 4,5,main]) completed. Took 0.008 secs.
:sessions-service:classes (Thread[Execution worker for ':' Thread 4,5,main]) started.

> Task :sessions-service:classes UP-TO-DATE
Skipping task ':sessions-service:classes' as it has no actions.
:sessions-service:classes (Thread[Execution worker for ':' Thread 4,5,main]) completed. Took 0.0 secs.
:sessions-service:compileTestKotlin (Thread[Execution worker for ':' Thread 4,5,main]) started.

> Task :sessions-service:compileTestKotlin UP-TO-DATE
Caching disabled for task ':sessions-service:compileTestKotlin' because:
  Build cache is disabled
Skipping task ':sessions-service:compileTestKotlin' as it is up-to-date.
:sessions-service:compileTestKotlin (Thread[Execution worker for ':' Thread 4,5,main]) completed. Took 0.133 secs.
:sessions-service:compileTestJava (Thread[Execution worker for ':' Thread 4,5,main]) started.

> Task :sessions-service:compileTestJava NO-SOURCE
file or directory '/Users/bbaldino/work/sessions/sessions-service/src/test/java', not found
Skipping task ':sessions-service:compileTestJava' as it has no source files and no previous output files.
:sessions-service:compileTestJava (Thread[Execution worker for ':' Thread 4,5,main]) completed. Took 0.002 secs.
:sessions-service:processTestResources (Thread[Execution worker for ':' Thread 4,5,main]) started.

> Task :sessions-service:processTestResources NO-SOURCE
file or directory '/Users/bbaldino/work/sessions/sessions-service/src/test/resources', not found
Skipping task ':sessions-service:processTestResources' as it has no source files and no previous output files.
:sessions-service:processTestResources (Thread[Execution worker for ':' Thread 4,5,main]) completed. Took 0.001 secs.
:sessions-service:testClasses (Thread[Execution worker for ':' Thread 4,5,main]) started.

> Task :sessions-service:testClasses UP-TO-DATE
Skipping task ':sessions-service:testClasses' as it has no actions.
:sessions-service:testClasses (Thread[Execution worker for ':' Thread 4,5,main]) completed. Took 0.0 secs.
:sessions-service:test (Thread[Execution worker for ':' Thread 4,5,main]) started.

> Task :sessions-service:test UP-TO-DATE
file or directory '/Users/bbaldino/work/sessions/sessions-service/build/classes/java/test', not found
Caching disabled for task ':sessions-service:test' because:
  Build cache is disabled
Skipping task ':sessions-service:test' as it is up-to-date.
:sessions-service:test (Thread[Execution worker for ':' Thread 4,5,main]) completed. Took 0.098 secs.

BUILD SUCCESSFUL in 9s
4 actionable tasks: 4 up-to-date
Watched directory hierarchies: [/Users/bbaldino/work/sessions]

[sam]

I mean like what is tests -i supposed to do ?

[bbaldino]

oh, ha

[sam]

is tests even a gradle command ?

[bbaldino]

i’m new to gradle, so i saw “tests” in gradlew tasks and figured it would be worth trying 🙂

[bbaldino]

check:

bbaldino@BBALDINO-M-8A1Z sessions % ./gradlew check

BUILD SUCCESSFUL in 6s
11 actionable tasks: 5 executed, 6 up-to-date

[sam]

there's test

[sam]

and check

[sam]

test is JVM only, check is MPP

[sam]

but check runs test so you can alwys use it

[bbaldino]

ah yes, sorry test is what i meant (and what i ran, just a typo here)

[sam]

you prob are missing some test setup in your build file

[bbaldino]

it’s a multi-module project, so maybe i am missing something there.

[bbaldino]

i have

tasks.withType<Test>().configureEach {
    useJUnitPlatform()
}

in the submodule…do i need something at the top level as well?

[sam]

allprojects {
   apply(plugin = "org.jetbrains.kotlin.jvm")

   repositories {
      mavenCentral()
      mavenLocal()
   }

   dependencies {
        testImplementation("io.kotest:kotest-runner-junit5:5.2.3")
      testImplementation("io.kotest:kotest-assertions-core:5.2.3")
      testImplementation("io.kotest:kotest-property:5.2.3")
      testImplementation("io.kotest:kotest-framework-datatest:5.2.3")
      testImplementation("io.kotest.extensions:kotest-extensions-testcontainers:1.3.1")
      testImplementation("org.testcontainers:postgresql:1.17.1")
      testImplementation("org.testcontainers:kafka:1.17.1")
      testImplementation("io.kotest.extensions:kotest-assertions-ktor:1.0.3")
      testImplementation("io.kotest.extensions:kotest-extensions-wiremock:1.0.3")
   }

   tasks.named<Test>("test") {
      useJUnitPlatform()
      testLogging {
         showExceptions = true
         showStandardStreams = true
         exceptionFormat = org.gradle.api.tasks.testing.logging.TestExceptionFormat.FULL
      }
   }
}

[sam]

I do that at the top level

[bbaldino]

but it’s weird that the green arrow in intellij also can’t seem to run the test

[sam]

yep

[sam]

that is weird

[sam]

You can always use hoplite for refeerence https://github.com/sksamuel/hoplite

[bbaldino]

you have that in top-level settings.gradle.kts?

[bbaldino]

ah ok, i see you have a build.gradle.kts at the top

[bbaldino]

hm, tried moving the tasks.named<Test>... into an allProjects block in a top-level build.gradle.kts, but still no luck

[bbaldino]

ok well this is weird: if i put a failing assert in the test and run it, the assert does hit. but if i remove it, i get “No tests found for given includes: [com.cisco.webex.cpaas.pvideo.logging.LogContextTest](filter.includeTestsMatching)”

[bbaldino]

./gradlew test also shows it if there’s a failing assert

[bbaldino]

do i need id("io.kotest") version "0.3.8" plugin?

[sam]

No

[sam]

No tests found for given includes: [com.cisco.webex.cpaas.pvideo.logging.LogContextTest](filter.includeTestsMatching

[sam]

if you're doing includes inside gradle it won't work

[sam]

take it out

[sam]

https://kotest.io/docs/next/framework/conditional/conditional-tests-with-gradle.html

[bbaldino]

i’m not doing any includes that i’m aware of

[bbaldino]

maybe it’s doing that in intellij’s run configuration for the test?

[bbaldino]

[bbaldino]

that’s what got generated from the green arrow

[sam]

Hmmm

[sam]

Do you have the intellij plugin

[sam]

That looks like the junit plugin

[bbaldino]

a kotest intellij plugin? let me check

[bbaldino]

yeah i do

[bbaldino]

but that’s the “gradle” test plugin i think

[bbaldino]

i don’t have any “run with kotest” option in the green arrow menu (not sure if that’s expected or not)

[sam]

Do you have green arrow on individual tests

[bbaldino]

yeah, haven’t tried those

[bbaldino]

will check

[bbaldino]

looks like that does work

[bbaldino]

and that generated a kotest run config

[bbaldino]

so i guess the issue is a class-level green arrow generated a gradle run config instead of a kotest one

[sam]

yeah

[sam]

must be something odd because kotest should offer an arrow on the spec class too

[bbaldino]

tried deleting the existing run config and restarting intellij, but no luck. still creates a gradle run config

[bbaldino]

it’s the kotest plugin that should do that? how does it hook in to those files? the dir is marked as a test root

[bbaldino]

i tried removing the kotest and re-installing. i did see this when intellij prompted me:

[bbaldino]

(sorry i couldn’t capture the whole thing, the dumb window couldn’t be resized)

[bbaldino]

i get the same thing when i try to install manually via the marketplace

[bbaldino]

ok, upgraded intellij and then was able to get the plugin re-installed. and i think i found the issue. in preferences -> build, execution, environment -> gradle i had to change “run tests using” from “gradle” to “intellij”

[sam]

The gradle should still work, it should show you kotest/gradle options. But at least you got it working.