Getting NoSuchMethodError org hamcrest Matcher describeMismatch when running test in IntelliJ 10 5

Question

I m using JUnit-dep 4 10 and Hamcrest 1 3 RC2   I ve created a custom matcher that looks like the following   public static class MyMatcher extends TypeSafeMatcher lt String gt         Override     protected boolean matchesSafely String s               implementation                Override     public void describeTo Description description               implementation                Override     protected void describeMismatchSafely String item  Description mismatchDescription                implementation              It works perfectly fine when run from the command line using Ant   But when run from IntelliJ  it fails with   java lang NoSuchMethodError  org hamcrest Matcher describeMismatch Ljava lang Object Lorg hamcrest Description  V     at org hamcrest MatcherAssert assertThat MatcherAssert java 18      at org hamcrest MatcherAssert assertThat MatcherAssert java 8      at com netflix build MyTest testmyStuff MyTest java 40    My guess is that it s using the wrong hamcrest MatcherAssert   How do I find which hamcrest MatcherAssert it s using  ie which jar file it s using for hamcrest MatcherAssert    AFAICT  the only hamcrest jars in my classpath is 1 3 RC2   Is IntelliJ IDEA using it s own copy of JUnit or Hamcrest   How do I output the runtime CLASSPATH that IntelliJ is using

User · Accepted Answer

The problem was that the wrong hamcrest Matcher  not hamcrest MatcherAssert  class was being used   That was being pulled in from a junit-4 8 dependency one of my dependencies was specifying   To see what dependencies  and versions  are included from what source while testing  run   mvn dependency tree -Dscope test

User · Answer

The following should be the most correct today  Note  junit 4 11 depends on hamcrest-core  so you shouldn t need to specify that at all  mockito-all cannot be used since it includes  not depends on  hamcrest 1 1   lt dependency gt       lt groupId gt junit lt  groupId gt       lt artifactId gt junit lt  artifactId gt       lt version gt 4 11 lt  version gt       lt scope gt test lt  scope gt   lt  dependency gt   lt dependency gt       lt groupId gt org mockito lt  groupId gt       lt artifactId gt mockito-core lt  artifactId gt       lt version gt 1 10 8 lt  version gt       lt scope gt test lt  scope gt       lt exclusions gt           lt exclusion gt               lt groupId gt org hamcrest lt  groupId gt               lt artifactId gt hamcrest-core lt  artifactId gt           lt  exclusion gt       lt  exclusions gt   lt  dependency gt

User · Answer

Despite the fact that this is a very old question and probably many of the beforementioned ideas solved many problems  I still want to share the solution with the community that fixed my problem   I found that the problem was a function called  hasItem  which I was using to check whether or not a JSON-Array contains a specific item  In my case I checked for a value of type Long   And this led to the problem   Somehow  the Matchers have problems with values of type Long   I do not use JUnit or Rest-Assured so much so idk  exactly why  but I guess that the returned JSON-data does just contain Integers    So what I did to actually fix the problem was the following  Instead of using   long ID              then   assertThat      body  myArray   hasItem ID      you just have to cast to Integer  So the working code looked like this   long ID              then   assertThat      body  myArray   hasItem  int  ID      That s probably not the best solution  but I just wanted to mention that the exception can also be thrown because of wrong unknown data types

User · Answer

This worked for me  No need to exclude anything  I just used mockito-core instead mockito-all  testCompile  junit junit 4 12  testCompile group   org mockito   name   mockito-core   version   3 0 0  testCompile group   org hamcrest   name   hamcrest-library   version   2 1

User · Answer

I know that s not the best answer  but if you can t get the classpath working  this is a plan B solution   In my test classpath  I added the following interface with a default implementation for the describeMismatch method   package org hamcrest          PATCH because there s something wrong with the classpath  Hamcrest should be higher than Mockito so that the BaseMatcher    implements the describeMismatch method  but it doesn t work for me       public interface Matcher lt T gt  extends SelfDescribing        boolean matches Object item        default void describeMismatch Object item  Description mismatchDescription            mismatchDescription appendDescriptionOf this  appendValue item               Deprecated     void  dont implement Matcher   instead extend BaseMatcher

User · Answer

I have a gradle project and when my build gradle dependencies section looks like this   dependencies       implementation group   org apache commons   name   commons-lang3   version   3 8 1       testImplementation group   org mockito   name   mockito-all   version   1 10 19      testImplementation  junit junit 4 12        testCompile group   org mockito   name   mockito-core   version   2 23 4       compileOnly  org projectlombok lombok 1 18 4      apt  org projectlombok lombok 1 18 4      it leads to this exception   java lang NoSuchMethodError  org hamcrest Matcher describeMismatch Ljava lang Object Lorg hamcrest Description  V      at org hamcrest MatcherAssert assertThat MatcherAssert java 18      at org hamcrest MatcherAssert assertThat MatcherAssert java 8    to fix this issue  I ve substituted  mockito-all  with  mockito-core    dependencies       implementation group   org apache commons   name   commons-lang3   version   3 8 1         testImplementation group   org mockito   name   mockito-all   version   1 10 19      testImplementation  junit junit 4 12      testCompile group   org mockito   name   mockito-core   version   2 23 4       compileOnly  org projectlombok lombok 1 18 4      apt  org projectlombok lombok 1 18 4      The explanation between mockito-all and mockito-core can be found here   https   solidsoft wordpress com 2012 09 11 beyond-the-mockito-refcard-part-3-mockito-core-vs-mockito-all-in-mavengradle-based-projects      mockito-all jar besides Mockito itself contains also  as of 1 9 5  two   dependencies  Hamcrest and Objenesis  let   s omit repackaged ASM and   CGLIB for a moment   The reason was to have everything what is needed   inside an one JAR to just put it on a classpath  It can look strange    but please remember than Mockito development started in times when   pure Ant  without dependency management  was the most popular build   system for Java projects and the all external JARs required by a   project  i e  our project   s dependencies and their dependencies  had   to be downloaded manually and specified in a build script       On the other hand mockito-core jar is just Mockito classes  also with   repackaged ASM and CGLIB   When using it with Maven or Gradle required   dependencies  Hamcrest and Objenesis  are managed by those tools    downloaded automatically and put on a test classpath   It allows to   override used versions  for example if our projects uses never  but   backward compatible version   but what is more important those   dependencies are not hidden inside mockito-all jar what allows to   detected possible version incompatibility with dependency analyze   tools  This is much better solution when dependency managed tool is   used in a project

User · Answer

This worked for me after struggling a bit   lt dependency gt       lt groupId gt org hamcrest lt  groupId gt       lt artifactId gt hamcrest-all lt  artifactId gt       lt version gt 1 3 lt  version gt       lt scope gt test lt  scope gt    lt  dependency gt     lt dependency gt       lt groupId gt org mockito lt  groupId gt       lt artifactId gt mockito-all lt  artifactId gt       lt version gt 1 9 5 lt  version gt       lt scope gt test lt  scope gt    lt  dependency gt     lt dependency gt       lt groupId gt junit lt  groupId gt       lt artifactId gt junit lt  artifactId gt       lt version gt 4 11 lt  version gt       lt scope gt test lt  scope gt    lt  dependency gt

User · Answer

I know this is an old thread but what solved the issue for me was adding the following to my build gradle files  As already stated above there is a compatibility issue with mockito-all  Possibly useful post   testCompile   junit junit 4 12         exclude group   org hamcrest    testCompile   org mockito mockito-core 1 10 19         exclude group   org hamcrest    testCompile  org hamcrest hamcrest-core 1 3

User · Answer

As of July  2020 the following dependencies in pom xml worked for me   lt dependency gt       lt groupId gt junit lt  groupId gt       lt artifactId gt junit lt  artifactId gt       lt version gt 4 13 lt  version gt   lt  dependency gt   lt dependency gt       lt groupId gt org hamcrest lt  groupId gt       lt artifactId gt hamcrest lt  artifactId gt       lt version gt 2 1 lt  version gt   lt  dependency gt   With this 4 13 junit library and hamcrest  it uses hamcrest MatcherAssert when asserting and throws exception- enter image description here

User · Answer

Try  expect new ThrowableMessageMatcher new StringContains message     instead of   expectMessage message   You may write a custom ExpectedException or utility method to wrap up the code

User · Answer

In my case  I had to exclude an older hamcrest from junit-vintage    lt dependency gt     lt groupId gt org junit vintage lt  groupId gt     lt artifactId gt junit-vintage-engine lt  artifactId gt     lt scope gt test lt  scope gt     lt exclusions gt       lt exclusion gt         lt groupId gt org hamcrest lt  groupId gt         lt artifactId gt hamcrest-core lt  artifactId gt       lt  exclusion gt     lt  exclusions gt   lt  dependency gt   lt dependency gt     lt groupId gt org hamcrest lt  groupId gt     lt artifactId gt hamcrest lt  artifactId gt     lt version gt 2 1 lt  version gt     lt scope gt test lt  scope gt   lt  dependency gt

User · Answer

What worked for me was excluding the hamcrest group from the junit test compile   Here is the code from my build gradle   testCompile   junit junit 4 11         exclude group   org hamcrest      If you re running IntelliJ you may need to run gradle cleanIdea idea clean build to detect the dependencies again

User · Answer

Make sure the hamcrest jar is higher on the import order than your JUnit jar   JUnit comes with its own org hamcrest Matcher class that is probably being used instead   You can also download and use the junit-dep-4 10 jar instead which is JUnit without the hamcrest classes   mockito also has the hamcrest classes in it as well  so you may need to move reorder it as well

User · Answer

This problem also arises when you have mockito-all on your class path  which is already deprecated   If possible just include mockito-core   Maven config for mixing junit  mockito and hamcrest    lt dependencies gt     lt dependency gt       lt groupId gt org hamcrest lt  groupId gt       lt artifactId gt hamcrest-core lt  artifactId gt       lt version gt 1 3 lt  version gt       lt scope gt test lt  scope gt     lt  dependency gt     lt dependency gt       lt groupId gt org hamcrest lt  groupId gt       lt artifactId gt hamcrest-library lt  artifactId gt       lt version gt 1 3 lt  version gt       lt scope gt test lt  scope gt     lt  dependency gt     lt dependency gt       lt groupId gt org mockito lt  groupId gt       lt artifactId gt mockito-all lt  artifactId gt       lt version gt 1 9 5 lt  version gt       lt scope gt test lt  scope gt     lt  dependency gt     lt dependency gt       lt groupId gt junit lt  groupId gt       lt artifactId gt junit lt  artifactId gt       lt version gt 4 11 lt  version gt       lt scope gt test lt  scope gt     lt  dependency gt   lt  dependencies gt

[java] Getting "NoSuchMethodError: org.hamcrest.Matcher.describeMismatch" when running test in IntelliJ 10.5

Examples related to java

Examples related to junit

Examples related to intellij-idea

Examples related to junit4

Examples related to hamcrest