Does anyone know if it's possible to make an

integrationTest

sourceSet but for KMP? I tried doing it (for JVM target only, but KMP would be even better) but the code (attached in thread) seems to break the

commonMain

&

commonTest

sourceSets.. It's in a private project, but I can recreate a reproducible for YouTrack if this is a bug.

sure it is possible, just create an additional compilation on each target you want it on

Please do not use ‘benchmark’.dependsOn(main). Use .associateWith instead!

I haven't touched that in a while, but IIRC

associateWith

resulted in duplicate class definitions

If this would still be the case, please file a bug! Probably interesting for @atyrin here. A dependsOn from one ‘SourceSetTree’ to another ‘SourceSetTree’ will be deprecated in 1.9.20 and removed in Kotlin 2.0

I work on aoc every december so when I revisit it this year, 1.9 should be out and I'll check that the new way works

😎 Deal! We will likely check as well when we deprecate the depends relation in this manner.

Okay,

associateWith

fixed it 🥳 Thank you. @Sebastian Sellmair [JB], does this look correct to you?

jvm {
  compilations {
    val integrationTest by compilations.creating {
      // Create a test task to run the tests produced by this compilation:
      tasks.register<Test>("integrationTest") {
        description = "Run the integration tests"
        group = "verification"
        classpath = compileDependencyFiles + runtimeDependencyFiles + output.allOutputs
        testClassesDirs = output.classesDirs

        testLogging {
          events("passed")
        }
      }
    }
    val test by compilations.getting
    integrationTest.associateWith(test)
  }
}

Btw can I still use

dependsOn

for creating a common native sourceSet 🤔?

create("nativeMain") {
  dependsOn(commonMain)
  linuxX64Main.dependsOn(this)
  macosX64Main.dependsOn(this)
  mingwX64Main.dependsOn(this)
}

Your code looks perfectly correct 👍 Yes you still can use dependsOn for exactly this use case. However, even this usage will be marked as

DelicateKotlinGradlePluginApi

and shall be replaced by

targetHierarchy.default()

,

targetHierarchy.custom

or similar. Also interesting: We plan that 1.9.20 will automatically create source sets like

nativeMain

for you 👍

Awesome, thank you so much for replying and clarifying my doubt @Sebastian Sellmair [JB]