java.lang.NoClassDefFoundError: org/junit/platform/commons/PreconditionViolationException when trying run junit5 test with maven

Remove junit-platform-launcher, junit-jupiter-engine and junit-jupiter-api.

Add junit-jupiter. (junit-jupiter is aggregator)

Sources:

• https://github.com/junit-team/junit5/issues/1773
• It worked for me.

adding following dependency helped in my case

 <dependency> <groupId>org.junit.platform</groupId> <artifactId>junit-platform-commons</artifactId> <version>1.5.2</version> </dependency> 

As others suggested, using JUnit 5.5.2 version is the way to go here. There are different alternatives to achieve this:

1. If you're using spring-boot-starter-parent, you can upgrade it to 2.2.0.RELEASE
2. If you use spring-boot-starter-parent (or spring-boot-dependencies), you can define a property to update just JUnit: <junit-jupiter.version>5.5.2</junit-jupiter.version>
3. If you're having this issue just in Eclipse, you can update it and add the JUnit 5 library to the Java Build Path (Project > Java Build Path > Libraries > Add Library > JUnit > JUnit 5 > Finish)
4. You can add the Junit BOM, using 5.5.2 version (see Prasanth Rajendran or Ramit answer)

I got the same problem with Gradle build and I got my issue resolved using the JUnit Bill of Materials(BOM), which will take care of Junit's direct and transitive dependencies version.

dependencyManagement { imports { mavenBom "org.junit:junit-bom:5.5.2" } } dependencies { ... testCompile('org.junit.jupiter:junit-jupiter-api') testRuntime('org.junit.jupiter:junit-jupiter-engine') testCompile('org.junit.jupiter:junit-jupiter-params') testCompile('org.junit.platform:junit-platform-launcher') testCompile('org.junit.platform:junit-platform-runner') } 

NOTE: I have not specified the version because the Junit BOM will take care of the Junit dependencies' version management role.

The following worked for me using surefire.plugin.version 2.22.2

junit-jupiter artifact brings in all other necessary artifacts.

<dependencyManagement> <dependencies> <dependency> <groupId>org.junit</groupId> <artifactId>junit-bom</artifactId> <version>5.5.2</version> <type>pom</type> <scope>import</scope> </dependency> </dependencies> </dependencyManagement> <dependencies> <dependency> <groupId>org.junit.jupiter</groupId> <artifactId>junit-jupiter</artifactId> <scope>test</scope> </dependency> <!--Optional: Supports running Junit4 along with Junit5 --> <dependency> <groupId>org.junit.vintage</groupId> <artifactId>junit-vintage-engine</artifactId> <scope>test</scope> </dependency> </dependencies> 

Few days ago I faced the similar issue. I tried all solutions suggested here, but none of them worked. In my case the error occurred because classpath ended up having two different versions of JUnit. I had spring-boot-test dependency wich uses JUnit 5.3.2. But then, I added JUnit 5.7.1. Therefore, my project was compiled with a newer version of JUnit (5.7.1) but found an older version (5.3.2) at runtime. As a result, the JUnit launcher tried to use a class that is not available in the older version of JUnit.In my case solution was to override the JUnit version managed by Spring like this:

<properties> <junit-jupiter.version>5.7.1</junit-jupiter.version> </properties> 

Hope somebody find this helpful.

Try upgrade the Junit to 5.8.2 or greater, see Jupter Junit versions availables here:

<!-- https://mvnrepository.com/artifact/org.junit.jupiter/junit-jupiter-api --> <dependency> <groupId>org.junit.jupiter</groupId> <artifactId>junit-jupiter-api</artifactId> <version>5.8.2</version> <scope>test</scope> </dependency> 

The junit-platform-commons is transactive dependency from Junit, so if you upgrade Junit these transactive dependencies will also be updated.

In my case the problem disappeared after deleting my local maven repository. Don't know what library caused this strange behaviour, but now everything is working fine!

java.lang.NoClassDefFoundError: org/junit/platform/commons/PreconditionViolationException when trying run junit5 test with maven

This error can be come due to the version mismatch of junit-plateform-engine junit-jupiter-params and junit-platform-runner and also other respective dependencies.

So for the resolution of this issue you do not need to define version like 1.5.3 ...etc

you can define version as follows :

<dependencies> <!--need to add for parameterized test --> <dependency> <groupId>org.junit.jupiter</groupId> <artifactId>junit-jupiter-params</artifactId> **<version>${junit.jupiter.version}</version>** <scope>test</scope> </dependency> <dependency> <groupId>org.junit.jupiter</groupId> <artifactId>junit-jupiter-engine</artifactId> **<version>${junit.jupiter.version}</version>** <scope>test</scope> </dependency> <dependency> <groupId>org.junit.platform</groupId> <artifactId>junit-platform-runner</artifactId> **<version>${junit.platform.version}</version>** <scope>test</scope> </dependency> </dependencies> 

So through this compatible version jar will be added in your project and project will run successfully

In case it helps anyone: I was getting similar error along with "No tests found with test runner JUnit 5" when running JUnit 5 tests in Eclipse (gradle-based). Upgrading to JUnit 5.6.0 helped as per https://github.com/eclipse/buildship/issues/980

You can get the error like "java.lang.NoClassDefFoundError: org/junit/platform/commons/util/Preconditions" in case of tring to included some test class (from junit/assertj) in your production code.

Above is a consequence of

• puttinh test library as a dependency NOT in scope test (so making it available at runtime)
• possibly following on above error you importing such test utility class in your production code - src/main/java (for example you used import like import org.assertj.core.util.Lists in your production code from src/main/java.
• the possibility is also that such test library was added as part of java9 module-info (like requires org.assertj.core)

NOTE: This offending dependency could be inside your module or any module included in dependencies.

For example your module has following dependency:

 <dependency> <groupId>com.acme</groupId> <artifactId>your-another-module</artifactId> </dependency> 

and your another module includes spring-boot-starter-test in scope compile like:

 <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-test</artifactId> <scope>compile</scope> <!-- **or even scope is omitted and by default it is compile !** --> <exclusions> <exclusion> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter</artifactId> </exclusion> <exclusion> <groupId>org.junit.vintage</groupId> <artifactId>junit-vintage-engine</artifactId> </exclusion> </exclusions> </dependency> 

As mentioned inside above code snippet, the scope might have even been omitted which would default to "compile".

Now following on that error you might have a production class YourClass residing in your module and accidentally import some test code from test libraries like:

// here we have accidential import of Lists from assertj import org.assertj.core.util.Lists; class YourClass { } 

The solution is to:

• fix the dependencies to make them in scope test and use correct imports in your production code
• clean up module-info.java from any test libraries which are not needed in your production code

I use gradle, Finally making below changes worked for me

Changed to ->

dependencies { testImplementation 'org.mockito:mockito-junit-jupiter:3.11.1' testImplementation 'org.junit.jupiter:junit-jupiter:5.7.2' 

}

from->

dependencies { testCompile 'org.mockito:mockito-junit-jupiter:3.3.3' testCompile 'org.junit.jupiter:junit-jupiter:5.4.2' } 

Older versions of JUnit Jupiter and/or Surefire did not integrate well. Use the latest if you can — combined with using simple configuration of minimal and consistent dependencies/plugins, it should eliminate this error entirely.

For example, this POM excerpt works well:

<project> <dependencyManagement> <dependencies> <dependency> <groupId>org.junit</groupId> <artifactId>junit-bom</artifactId> <version>5.10.2</version> <type>pom</type> <scope>import</scope> </dependency> </dependencies> </dependencyManagement> <dependencies> <dependency> <groupId>org.junit.jupiter</groupId> <artifactId>junit-jupiter-api</artifactId> <scope>test</scope> </dependency> <!-- can add junit-jupiter-params, etc. --> <!-- don't depend on the engine; Surefire manages it --> </dependencies> <build> <pluginManagement> <plugins> <plugin> <groupId>org.apache.maven</groupId> <artifactId>maven-surefire-plugin</artifactId> <version>3.3.0</version> </plugin> </plugins> </pluginManagement> <plugins> <plugin> <groupId>org.apache.maven</groupId> <artifactId>maven-surefire-plugin</artifactId> <version>3.3.0</version> </plugin> </plugins> </build> </project> 

I have commented the below part in pom.xml:

 <dependency> <groupId>org.junit.jupiter</groupId> <artifactId>junit-jupiter-api</artifactId> <version>5.3.2</version> <scope>test</scope> </dependency> <dependency> <groupId>org.junit.jupiter</groupId> <artifactId>junit-jupiter-engine</artifactId> <version>5.3.2</version> <scope>test</scope> </dependency> 

And I have added junit5 in java build path(project(right click->java build path->libraries->junit->junit5) It worked for me. Mine is spring-boot project.