A modern programming language that makes developers happier.

kotlinlang

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

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

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`

Interestingly, this doesn’t work
```getByName("commonMain") {
      dependencies {
        implementation("org.jetbrains.kotlin:kotlin-test")
      }
    }
    getByName("commonTest") {
      dependencies {
        implementation("org.jetbrains.kotlin:kotlin-test")
      }
    }```


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

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`

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

My current understanding is that adding `kotlin-test` to `commonMain` triggers <https://github.com/JetBrains/kotlin/blob/e84e83568cde569ee54980542e37c87507e914bc/libraries/tools/kotlin-gradle-plugin/src/common/kotlin/org/jetbrains/kotlin/gradle/internal/kotlinTestDependencyManagement.kt#L111|maybeAddTestDependencyCapability> “earlier” (`testCapability` is null there) and therefore prevents the automatic adding of `kotlin-test-junit5`