Kotlin-DSL-Samples | This Repo contains samples of Kotlin DSLs

To establish a dependency of this sort between single-platform projects, you would normally need to create a Gradle Configuration in the producer project, add the test compilation outputs or a test JAR into that configuration, and, in the consumer project, depend on that configuration (i.e. add a project(...) dependency with an explicit configuration or, more preferrable, add attributes to ensure that Gradle chooses the test-outputs configuration in variant-aware dependency resolution).

However, all of this requires that tests are compiled to a form that could be reused by the consumer project's common source sets. With Kotlin Multiplatform projects, this is not yet the case. While the production common source sets, which participate in published compilations, are compiled to Kotlin metadata (*.kotlin_metadata files), test sources and other kinds of non-published code are not yet transformed to that format.

Instead, tests are currently only compiled to the final platform-specific binaries (i.e. *.class files, *.js, Native binaries), which cannot be used for common sources analysis.

Therefore, dependencies of this kind are not supported yet. This could change in the future. Please follow this issue in the Kotlin issue tracker: KT-35073.