A modern programming language that makes developers happier.

kotlinlang

Is there any way to debug why a test suite isn't being picked up when running tests (either via gradle or IDEA plugin)?

image.png

Doesn't seem to matter what I call it, however there is another suite in the same package that _does_ get picked up (declared the same way)

Is it on the JVM? In that case, the Gradle build cache could cause irritations if Gradle decides that tests are "UP-TO-DATE".

even forcing rerun it doesn't pick it up - I'll try killilng/clearing kotlin caches

If it's not Gradle, the next step could be to check if the compiler plugin discovers the top-level suite. You could put that into your build script:
```testBalloon {
    debugLevel = DebugLevel.DISCOVERY
}```
...and check the build output.

it seems to be to do with incremental compilation :thinking_face:

Which Kotlin and TestBalloon versions are you using? Could you publish a reproducer on GitHub?

I was on (I just found) Kotlin 2.2.20 and testBallon 0.7.1-K2.2.21, but it happens with Kotlin 2.2.21 too. Hopefully have a tiny reproducer for you shortly

<https://github.com/tKe/testBalloon-vanishing-suites>
run the tests (`./gradlew test --rerun`) and both get logged
rename one of the test suite properties (i.e. `val firstSuite` -> `val firstSuites`)
run the tests (`./gradlew test --rerun`) and only the renamed suite gets run
run the tests with `-Pkotlin.incremental=false` and they both get logged again

Cool, I'll look into it. TestBalloon has integration tests that verify incremental compilation, but maybe we have an edge case here that's not covered by those.

So you rename just the suite property, and leave the file names as is, right?

Reproduced. Thank you! That's probably some food for the Kotlin compiler folks.

<https://youtrack.jetbrains.com/issue/KT-82560>