I know I could create bundles for this, but is there another good way to share dependencies between jvm test suites (like, I'd presume something like 90% overlap)

testing {
  suites {
    val test by getting(JvmTestSuite::class) {
      dependencies {
        implementation(platform(libs.spring.bom))
        implementation(libs.junit.api)
        implementation(libs.assertj)
        implementation(libs.vavr)
        implementation(project(path))

        runtimeOnly(platform(libs.spring.bom))
        runtimeOnly(libs.junit.engine)
        runtimeOnly(libs.junit.launcher)
      }
    }
    val whitebox by getting(JvmTestSuite::class) {
      dependencies {
        implementation(platform(libs.spring.bom))
        implementation(libs.junit.api)
        implementation(libs.assertj)
        implementation(libs.vavr)
        implementation(project(path))

        runtimeOnly(platform(libs.spring.bom))
        runtimeOnly(libs.junit.engine)
        runtimeOnly(libs.junit.launcher)
      }
    }
  }
}

I'll usually do that via convention plugins that will just add the common set of deps/config for me. IE: junit5 config, assertion lib, logger impl lib etc

Why not declare

dependencies

directly on the

JvmTestSuite

like https://github.com/oss-review-toolkit/ort/blob/f9d3bd0e93b5260f4f86f951246c7c9fa15[…]d1f1/buildSrc/src/main/kotlin/ort-kotlin-conventions.gradle.kts?

well... in this case it's currently only in this 1 subproject, like 2 or 3 test suites in this one subproject using test suites.

I sometimes use

java-test-fixtures

, and then expose the common dependencies using

testFixturesApi()

. Then in each test suite do

implementation(testFixtures(project()))

https://docs.gradle.org/current/userguide/jvm_test_suite_plugin.html#method_3_extract_a_custom_configuration_block <-- you could try configuring like this example as well