From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

If I am seeing errors like this after updating junit to 5.12.0 does that mean that Gradle doesn't support it yet, or is there something else wrong?

```Caused by: org.junit.platform.commons.JUnitException: OutputDirectoryProvider not available; probably due to unaligned versions of the junit-platform-engine and junit-platform-launcher jars on the classpath/module path.```


did you specify both platform-engine/launcher yourself?

I haven't specified launcher. I just use:

```tasks.withType&lt;Test&gt; {
  useJUnitPlatform()
  outputs.upToDateWhen { false }
}```

there was a thing a while ago that said support for not specifying was going away... if you're not using any other kind of bom, I highly recommend using junits

libs.versions.toml
```[libraries]
junit-api = { module = "org.junit.jupiter:junit-jupiter-api" }
junit-bom = "org.junit:junit-bom:5.+"
junit-parameters = { module = "org.junit.jupiter:junit-jupiter-params" }
junit-engine = { module = "org.junit.jupiter:junit-jupiter-engine" }
junit-launcher = { module = "org.junit.platform:junit-platform-launcher" }
[bundles]
test-impl = ["junit-api", "assertj", "junit-parameters"]
test-runtime = ["junit-engine", "junit-launcher"]```


This is what Caleb means: <https://docs.gradle.org/current/userguide/upgrading_version_8.html#test_framework_implementation_dependencies|https://docs.gradle.org/current/userguide/upgrading_version_8.html#test_framework_implementation_dependencies>

this is syntax for jvm test suite, adapt accordingly :wink:
```        implementation(platform(libs.junit.bom))
        implementation.bundle(libs.bundles.test.impl)
        runtimeOnly.bundle(libs.bundles.test.runtime)```

note: I'm not 100% certain this is your problem, but it should fix it

I think it is, also was my first thought, just searched for the link first. :-D