Looks like adding `kotlin-test` as a `commonMain` dependency makes `compileTestKotlinJvm` fail with ...

# test

[mbonnin]

Looks like adding kotlin-test as a commonMain dependency makes compileTestKotlinJvm fail with Unresolved reference 'kotlin.test.Test'? Is that expected?

[ephemient]

needs kotlin-test-junit5 or one of the other variants to `avtual`ize the `expect`ed types on JVM

[ephemient]

I think KGP sets that up to happen automatically if it's in commonTest, maybe it doesn't work if you put it in commonMain

[mbonnin]

That was it, thanks!

[mbonnin]

Interestingly, this doesn’t work

getByName("commonMain") {
      dependencies {
        implementation("org.jetbrains.kotlin:kotlin-test")
      }
    }
    getByName("commonTest") {
      dependencies {
        implementation("org.jetbrains.kotlin:kotlin-test")
      }
    }

[mbonnin]

But this does

getByName("commonMain") {
      dependencies {
        implementation("org.jetbrains.kotlin:kotlin-test")
      }
    }
    getByName("commonTest") {
      dependencies {
        implementation("org.jetbrains.kotlin:kotlin-test-junit5")
      }
    }

[ephemient]

well the usual thing would be

commonTest {
  dependencies {
    implementation(kotlin("test"))
  }
}
jvmTest {
  dependencies {
    implementation(kotlin("test-junit5"))
  }
}

and I guess you're doing it in commonMain for some reason instead of commonTest, but then I'd put the JVM dependency in jvmMain

[mbonnin]

I want to use assertFoo in commonMain because this is code that I want to publish and use from other tests. Ideally I would use test fixtures but haven’t been able to so far

[mbonnin]

My current understanding is that adding kotlin-test to commonMain triggers maybeAddTestDependencyCapability “earlier” (testCapability is null there) and therefore prevents the automatic adding of kotlin-test-junit5

[mbonnin]

Anyways, it’s all working now, thanks!