Am I correct that kotest doesn’t support coroutine...

# kotest

[iamsteveholmes]

Am I correct that kotest doesn’t support coroutines -native-mt? I’m getting this in my gradle dependencies:

+--- org.jetbrains.kotlinx:kotlinx-coroutines-core:{strictly 1.6.0-native-mt} FAILED

[sam]

What do you mean support it.

[iamsteveholmes]

Well my dependencies are confusing me at the moment. The list of runtime dependencies seems to force resolve coroutines core to 1.6.0 and that appears to mess up many of the libraries that depend on 1.6.0-native-mt. However, as far as I can tell the compile dependencies resolve as I would expect them to to native-mt.

So releaseUnitTestRuntimeClasspath seems to resolve to 1.6.0 while releaseUnitTestCompileClasspath resolves to 1.6.0-native-mt. Any idea why it would differ?

[sam]

No that doesn't make much sense to me either

[iamsteveholmes]

Does kotest require a JVM target? I see that the sample projects always seem to have a JVM target. By default KMM doesn’t add a JVM target, although tests that run under commonTest execute on the JVM.

[sam]

nope

[sam]

you can JS only for instance

[sam]

or native only

[sam]

https://github.com/kotest/kotest-examples-javascript

[iamsteveholmes]

I’ve configured kotest in the commonTest sourceSet:

val commonTest by getting {
            dependencies {
                implementation(kotlin("test"))
                implementation(kotlin("test-common"))
                implementation(kotlin("test-annotations-common"))
                implementation("org.jetbrains.kotlinx:kotlinx-coroutines-test:$coroutines_version")
                implementation("io.kotest:kotest-assertions-core:$kotest_version")
                implementation("io.kotest:kotest-framework-engine:$kotest_version")
                implementation("io.kotest:kotest-framework-datatest:$kotest_version")
                implementation("io.kotest:kotest-assertions-core:$kotest_version")
            }
        }

[sam]

looks fine

[sam]

you're mixing kotlin test and kotest though, any reason ?

[iamsteveholmes]

All my current tests were built using kotlin test. I was trying to add kotest with the plan to eventually phase out/replace existing tests.

[sam]

ah ok

[sam]

I don't know what native-mt does to be honest, but you could try adding the rest of the kotlin coroutine deps that kotest uses, and using the version you want

[sam]

const val debug = "org.jetbrains.kotlinx:kotlinx-coroutines-debug:_"
const val coreCommon = "org.jetbrains.kotlinx:kotlinx-coroutines-core:_"
const val coreJvm = "org.jetbrains.kotlinx:kotlinx-coroutines-core-jvm:_"
const val coreNative = "org.jetbrains.kotlinx:kotlinx-coroutines-core-native:_"
const val jdk8 = "org.jetbrains.kotlinx:kotlinx-coroutines-jdk8:_"
const val test = "org.jetbrains.kotlinx:kotlinx-coroutines-test:_"

[sam]

you won't need jdk8 or jvm

[iamsteveholmes]

I’ve already got:

implementation("org.jetbrains.kotlinx:kotlinx-coroutines-core:$coroutines_version") {
                    version { strictly(coroutines_version) }
                }

[iamsteveholmes]

Under commonMain

[sam]

yeah that's just core though

[sam]

oh I see

[sam]

I guess the other one is debug

[iamsteveholmes]

My runtime dependency failures appear to be on core and not debug 🤨

[sam]

wouldn't hurt to have them all on the same though

[iamsteveholmes]

Ahhhh….just tried it out on a brand new project and it fails there too…

[iamsteveholmes]

Let me see if I can push it to github and you can see it

[iamsteveholmes]

https://github.com/iamsteveholmes/KotestNativeMt

[iamsteveholmes]

If you clone that repo and run ./gradlew :shared:dependencies you’ll see what I mean

[iamsteveholmes]

@sam Thank you so much for your help with this 😀

[sam]

* What went wrong:
Could not determine the dependencies of task 'androidApptestDebugUnitTest'.

SDK location not found. Define location with an ANDROID_SDK_ROOT environment variable or by setting the sdk.dir path in your project's local properties file at '/home/sam/development/workspace/KotestNativeMt/local.properties'.

[iamsteveholmes]

Ahhh…yes I have a local.properties with:

sdk.dir=/Users/steve/Library/Android/sdk

[sam]

can you fix the repo and I'll repull

[sam]

it'll need to auto install android

[sam]

I don't have it locally

[iamsteveholmes]

KMM generates it for you but it needs to be set by each individual user

[sam]

ok

[sam]

I'm also on linux so the ios stuff won't do much

[sam]

So what should I set my sdk.dir to be ? and where should I put it

[iamsteveholmes]

I think I just installed Android Studio and it placed it for me automagically.

[iamsteveholmes]

Not sure on linux where that is supposed to be.

[sam]

ok, then I guess can you make this issue without android ?

[iamsteveholmes]

I would think so

[iamsteveholmes]

Let me see….

[sam]

might help if it's just a boring native build wihtout android or ios

[iamsteveholmes]

Well that’s interesting…when I remove android the problem goes away….maybe there is an android configuration I need?

[sam]

oh there's lots of issues with androids 'unique' (ab)use of gradle

[sam]

I'm not an android user myself but I've seen issues before with this runtime and compile time classpath thing. If you delve through the kotest channel history, you might find something useful.

[sam]

Or ask a specific question at the top level around android configs and wait for someone to see next week

[iamsteveholmes]

working on it… doesn’t seem to like this from the docs:

android.testOptions {
    unitTests.all {
        useJUnitPlatform()
    }
}

[iamsteveholmes]

@sam I got it working by switching to 1.6.0 without the native-mt. Unfortunately some libraries still require it but for me they seem to be working with the switch so fingers crossed. I think 1.7 is deprecating native-mt. But it might make sense to update kotest docs around coroutines.