It seems that `commonTest`s are reported (at least in IDEA's UI) differently whether they are ran fr...

# kotest

[Didier Villevalois]

It seems that `commonTest`s are reported (at least in IDEA's UI) differently whether they are ran from jsTest or linuxX64Test compared to jvmTest. When they are ran in jvmTest, they are reported with their fully-qualified names (e.g. org.zeromq.sockets.PushPullTests), whereas, when ran from jsTest or linuxX64Test, they are reported with their simple class names (e.g. PushPullTests). Is there a way to fix the names on the JS and native targets to use the fully-qualified names?

[Emil Kantis]

I guess for JVM your tests are running with the Junit5 runner which might be reporting differently than however native/JS tests are done? Perhaps you could create an issue and include how your setup looks? 🙏

[Oliver.O]

The root cause on Js is probably that fully qualified class names are unavailable, just simple ones.
https://kotlinlang.org/api/latest/jvm/stdlib/kotlin.reflect/-k-class/qualified-name.html

[Didier Villevalois]

Indeed, that won't help... It seems I will have to live with it! @Emil Kantis do you still think it is worth opening a ticket?

Here's the setup:
• https://github.com/ptitjes/kzmq/blob/main/build.gradle.kts
• https://github.com/ptitjes/kzmq/blob/main/kzmq-tests/build.gradle.kts

[Emil Kantis]

Probably not. Could be worth a shot to check if Jetbrains kotlin.test package has any good solution for this, but if they don't either I guess it won't be possible to do anything about it.

[Didier Villevalois]

@Emil Kantis, indeed they do have a solution for this. When I add a kotlin.test test is it reported with its qualified name, even on JS target. I am not sure where to look for how they do that though!

[Emil Kantis]

Cool, thanks for checking. Then I think it's worth creating the ticket 🙂 Whoever picks it up can investigate how they solved it