Maven does not find JUnit tests to run

Question

I have a maven program  it compiles fine   When I run mvn test it does not run any tests  under TESTs header says There are no tests to run       I ve recreated this problem with a super simple setup which I will include below as well as the output when run with -X   The unit tests run fine from eclipse  both with its default junit package and when I instead include the junit jar downloaded by maven    Also mvn test-compile correctly creates the class under test-classes   I am running this on OSX 10 6 7 with Maven 3 0 2 and java 1 6 0 24   Here is the directory structure    my program pom xml  my program src main java ClassUnderTest java  my program src test java ClassUnderTestTests java   pom xml    lt  xml version  1 0  encoding  UTF-8   gt   lt project xmlns  http   maven apache org POM 4 0 0  xmlns xsi  http   www w3 org 2001 XMLSchema-instance  xsi schemaLocation  http   maven apache org POM 4 0 0 http   maven apache org maven-v4 0 0 xsd  gt       lt modelVersion gt 4 0 0 lt  modelVersion gt       lt groupId gt my group lt  groupId gt       lt artifactId gt my program lt  artifactId gt       lt packaging gt jar lt  packaging gt       lt version gt 1 0-SNAPSHOT lt  version gt       lt name gt My Program lt  name gt       lt dependencies gt           lt dependency gt               lt groupId gt junit lt  groupId gt               lt artifactId gt junit lt  artifactId gt               lt version gt 4 8 1 lt  version gt               lt scope gt test lt  scope gt           lt  dependency gt       lt  dependencies gt       lt build gt           lt plugins gt               lt plugin gt                   lt groupId gt org apache maven plugins lt  groupId gt                   lt artifactId gt maven-compiler-plugin lt  artifactId gt                   lt configuration gt                       lt source gt 1 5 lt  source gt                       lt target gt 1 5 lt  target gt                   lt  configuration gt               lt  plugin gt           lt  plugins gt       lt  build gt   lt  project gt    ClassUnderTest java   public class ClassUnderTest        public int functionUnderTest int n            return n             ClassUnderTestTests java   import org junit Assert  import org junit Before  import org junit Test   public class ClassUnderTestTests        private ClassUnderTest o        Before     public void setUp             o   new ClassUnderTest                Test     public void testFunctionUnderTest testCase1             Assert assertEquals 1  o functionUnderTest 1                Test     public void testFunctionUnderTest testCase2             Assert assertEquals 2  o functionUnderTest 2              End of mvn -X test    DEBUG  Configuring mojo org apache maven plugins maven-surefire-plugin 2 7 1 test from plugin realm ClassRealm plugin gt org apache maven plugins maven-surefire-plugin 2 7 1  parent  sun misc Launcher AppClassLoader 5224ee   DEBUG  Configuring mojo  org apache maven plugins maven-surefire-plugin 2 7 1 test  with basic configurator -- gt   DEBUG     s  basedir    Users aaron Programs my program  DEBUG     s  childDelegation   false  DEBUG     s  classesDirectory    Users aaron Programs my program target classes  DEBUG     s  disableXmlReport   false  DEBUG     s  enableAssertions   true  DEBUG     s  forkMode   once  DEBUG     s  junitArtifactName   junit junit  DEBUG     s  localRepository          id  local       url  file    Users aaron  m2 repository     layout  none   DEBUG     f  parallelMavenExecution   false  DEBUG     s  pluginArtifactMap    org apache maven plugins maven-surefire-plugin org apache maven plugins maven-surefire-plugin maven-plugin 2 7 1   org apache maven surefire surefire-booter org apache maven surefire surefire-booter jar 2 7 1 compile  org apache maven surefire surefire-api org apache maven surefire surefire-api jar 2 7 1 compile  org apache maven surefire maven-surefire-common org apache maven surefire maven-surefire-common jar 2 7 1 compile  org apache maven shared maven-common-artifact-filters org apache maven shared maven-common-artifact-filters jar 1 3 compile  org codehaus plexus plexus-utils org codehaus plexus plexus-utils jar 2 0 5 compile  junit junit junit junit jar 3 8 1 compile  org apache maven reporting maven-reporting-api org apache maven reporting maven-reporting-api jar 2 0 9 compile   DEBUG     s  printSummary   true  DEBUG     s  project   MavenProject  my group my program 1 0-SNAPSHOT    Users aaron Programs my program pom xml  DEBUG     s  projectArtifactMap    junit junit junit junit jar 4 8 1 test   DEBUG     s  redirectTestOutputToFile   false  DEBUG     s  remoteRepositories           id  central       url  http   repo1 maven org maven2    layout  default snapshots   enabled   gt  false  update   gt  daily   releases   enabled   gt  true  update   gt  never     DEBUG     s  reportFormat   brief  DEBUG     s  reportsDirectory    Users aaron Programs my program target surefire-reports  DEBUG     s  session   org apache maven execution MavenSession dfbb43  DEBUG     s  skip   false  DEBUG     s  skipTests   false  DEBUG     s  testClassesDirectory    Users aaron Programs my program target test-classes  DEBUG     s  testFailureIgnore   false  DEBUG     s  testNGArtifactName   org testng testng  DEBUG     s  testSourceDirectory    Users aaron Programs my program src test java  DEBUG     s  trimStackTrace   true  DEBUG     s  useFile   true  DEBUG     s  useManifestOnlyJar   true  DEBUG     s  workingDirectory    Users aaron Programs my program  DEBUG  -- end configuration --  INFO  Surefire report directory   Users aaron Programs my program target surefire-reports  DEBUG  Setting system property  user dir    Users aaron Programs my program   DEBUG  Setting system property  localRepository    Users aaron  m2 repository   DEBUG  Setting system property  basedir    Users aaron Programs my program   DEBUG  Using JVM   System Library Java JavaVirtualMachines 1 6 0 jdk Contents Home bin java  DEBUG  Using manager EnhancedLocalRepositoryManager with priority 10 for  Users aaron  m2 repository  DEBUG  dummy dummy jar 1 0  selected for null   DEBUG    org apache maven surefire surefire-booter jar 2 7 1 compile  selected for compile   DEBUG      org apache maven surefire surefire-api jar 2 7 1 compile  selected for compile   DEBUG  Adding to surefire booter test classpath   Users aaron  m2 repository org apache maven surefire surefire-booter 2 7 1 surefire-booter-2 7 1 jar Scope  compile  DEBUG  Adding to surefire booter test classpath   Users aaron  m2 repository org apache maven surefire surefire-api 2 7 1 surefire-api-2 7 1 jar Scope  compile  DEBUG  Using manager EnhancedLocalRepositoryManager with priority 10 for  Users aaron  m2 repository  DEBUG  dummy dummy jar 1 0  selected for null   DEBUG    org apache maven surefire surefire-junit4 jar 2 7 1 test  selected for test   DEBUG      org apache maven surefire surefire-api jar 2 7 1 test  selected for test   DEBUG  Adding to surefire test classpath   Users aaron  m2 repository org apache maven surefire surefire-junit4 2 7 1 surefire-junit4-2 7 1 jar Scope  test  DEBUG  Adding to surefire test classpath   Users aaron  m2 repository org apache maven surefire surefire-api 2 7 1 surefire-api-2 7 1 jar Scope  test  DEBUG  Test Classpath    DEBUG     Users aaron Programs my program target test-classes  DEBUG     Users aaron Programs my program target classes  DEBUG     Users aaron  m2 repository junit junit 4 8 1 junit-4 8 1 jar  DEBUG  Using manager EnhancedLocalRepositoryManager with priority 10 for  Users aaron  m2 repository  DEBUG  dummy dummy jar 1 0  selected for null   DEBUG    org apache maven surefire surefire-booter jar 2 7 1 compile  selected for compile   DEBUG      org apache maven surefire surefire-api jar 2 7 1 compile  selected for compile   DEBUG  Adding to surefire booter test classpath   Users aaron  m2 repository org apache maven surefire surefire-booter 2 7 1 surefire-booter-2 7 1 jar Scope  compile  DEBUG  Adding to surefire booter test classpath   Users aaron  m2 repository org apache maven surefire surefire-api 2 7 1 surefire-api-2 7 1 jar Scope  compile Forking command line   bin sh -c cd  Users aaron Programs my program  amp  amp   System Library Java JavaVirtualMachines 1 6 0 jdk Contents Home bin java -jar  Users aaron Programs my program target surefire surefirebooter6118081963679415631 jar  Users aaron Programs my program target surefire surefire4887918564882595612tmp  Users aaron Programs my program target surefire surefire9012255138269731406tmp  -------------------------------------------------------  T E S T S ------------------------------------------------------- There are no tests to run   Results    Tests run  0  Failures  0  Errors  0  Skipped  0   INFO  ------------------------------------------------------------------------  INFO  BUILD SUCCESS  INFO  ------------------------------------------------------------------------  INFO  Total time  2 089s  INFO  Finished at  Mon May 30 12 03 09 EDT 2011  INFO  Final Memory  7M 62M  INFO  ------------------------------------------------------------------------

User · Answer

Another easily overlooked problem I recently experienced - Ensure your Test class  file has the  java extension  If there s no tests to compile  there are no tests to run

User · Answer

Another reason for not running the test cases happened to me - I had a property named  test  for completely different purposes  but it interfered with the surefire plugin  Thus  please check your POMs for    lt properties gt     lt test gt       lt  test gt         lt  properties gt    and remove it

User · Answer

Check that  for jUnit - 4 12 and Eclipse surefire plugin    Add required jUnit version in POM xml in dependencies  Do Maven -  Update project to see required jars exported in project  Test class is under the folder src test java and subdirectories of this folder  or base folder can be specified in POM in config testSourceDirectory   Name of the class should have tailng word  Test   Test Method in the test class should have annotation  Test

User · Answer

Such problem might occur when you use surfire plugin 3 x x  with JUnit5 and by mistake annotate the test class with  Test annotation from JUnit4   Use  org junit jupiter api Test  JUnit5  instead of org junit Test  Junit4   NOTE  this might be hard to notice as the IDE might run this wihout problems just as JUnit4 test

User · Answer

Discovered if you prefix a test with  Abstract  it will be ignored by default aswell

User · Answer

If you have written your tests in JUnit 4 and added JUnit 5 dependencies to the surefire plugin  your tests will not run   In that case  just comment JUnit 5 dependencies from surefire plugin            lt plugin gt               lt groupId gt org apache maven plugins lt  groupId gt               lt artifactId gt maven-surefire-plugin lt  artifactId gt               lt version gt 2 19 1 lt  version gt               lt  -- lt dependencies gt -- gt                   lt  -- lt dependency gt -- gt                       lt  -- lt groupId gt org junit platform lt  groupId gt -- gt                       lt  -- lt artifactId gt junit-platform-surefire-provider lt  artifactId gt -- gt                       lt  -- lt version gt 1 0 0 lt  version gt -- gt                   lt  -- lt  dependency gt -- gt                   lt  -- lt dependency gt -- gt                       lt  -- lt groupId gt org junit jupiter lt  groupId gt -- gt                       lt  -- lt artifactId gt junit-jupiter-engine lt  artifactId gt -- gt                       lt  -- lt version gt   junit version  lt  version gt -- gt                   lt  -- lt  dependency gt -- gt               lt  -- lt  dependencies gt -- gt           lt  plugin gt

User · Answer

i used using this code   lt sourceDirectory gt src controller lt  sourceDirectory gt     lt testSourceDirectory gt src test lt  testSourceDirectory gt    to my pom xml  just ensure that testng file in specific there   lt suiteXmlFile gt  Users mac xxx xxx xx xxxx xx xxx restassured xx testng xml lt  suiteXmlFile gt

User · Answer

Here s the exact code I had to add to my pom xml        lt build gt       lt plugins gt           lt plugin gt               lt groupId gt org apache maven plugins lt  groupId gt               lt artifactId gt maven-surefire-plugin lt  artifactId gt               lt version gt 2 21 0 lt  version gt               lt dependencies gt                   lt dependency gt                       lt groupId gt org junit platform lt  groupId gt                       lt artifactId gt junit-platform-surefire-provider lt  artifactId gt                       lt version gt 1 2 0-M1 lt  version gt                   lt  dependency gt                   lt dependency gt                       lt groupId gt org junit jupiter lt  groupId gt                       lt artifactId gt junit-jupiter-engine lt  artifactId gt                       lt version gt 5 2 0 lt  version gt                   lt  dependency gt               lt  dependencies gt           lt  plugin gt       lt  plugins gt   lt  build gt    And here s my dependencies        lt dependencies gt       lt dependency gt           lt groupId gt org junit jupiter lt  groupId gt           lt artifactId gt junit-jupiter-api lt  artifactId gt           lt version gt 5 2 0 lt  version gt           lt scope gt test lt  scope gt       lt  dependency gt       lt dependency gt           lt groupId gt org easytesting lt  groupId gt           lt artifactId gt fest-assert-core lt  artifactId gt           lt version gt 2 0M10 lt  version gt           lt scope gt test lt  scope gt       lt  dependency gt       lt dependency gt           lt groupId gt org junit platform lt  groupId gt           lt artifactId gt junit-platform-surefire-provider lt  artifactId gt           lt version gt 1 2 0-M1 lt  version gt       lt  dependency gt       lt dependency gt           lt groupId gt org junit jupiter lt  groupId gt           lt artifactId gt junit-jupiter-engine lt  artifactId gt           lt version gt 5 2 0-M1 lt  version gt       lt  dependency gt   lt  dependencies gt

User · Answer

I also had similar issue  after exploring found that testng dependency is causing this issue  After removing the testng dependency from pom  as I dont need it anymore   it started to work fine for me        lt dependency gt           lt groupId gt org testng lt  groupId gt           lt artifactId gt testng lt  artifactId gt           lt version gt 6 8 lt  version gt           lt scope gt test lt  scope gt       lt  dependency gt

User · Answer

my program src test java ClassUnderTestTests java   should be    my program src test java ClassUnderTestTest java   The Maven finds those ends Test or starts with Test to run automatically   However  you can using   mvn surefire test -Dtest ClassUnderTestTests java    to run your tests

User · Answer

In my case we are migration multimodule application to Spring Boot  Unfortunately maven didnt execute all tests anymore in the modules  The naming of the Test Classes didnt change  we are following the naming conventions   At the end it helped  when I added the dependency surefire-junit47 to the plugin maven-surefire-plugin  But I could not explain  why  it was trial and error    lt plugin gt   lt groupId gt org apache maven plugins lt  groupId gt   lt artifactId gt maven-surefire-plugin lt  artifactId gt   lt dependencies gt     lt dependency gt       lt groupId gt org apache maven surefire lt  groupId gt       lt artifactId gt surefire-junit47 lt  artifactId gt       lt version gt   maven-surefire-plugin version  lt  version gt     lt  dependency gt   lt  dependencies gt

User · Answer

Another thing that can cause Maven to not find the tests if if the module s packaging is not declared correctly   In a recent case  someone had  lt packaging gt pom lt  packaging gt  and my tests never ran  I changed it to  lt packaging gt jar lt  packaging gt  and now it works fine

User · Answer

In my case  my parent pom had a parent   lt parent gt       lt groupId gt org springframework boot lt  groupId gt       lt artifactId gt spring-boot-starter-parent lt  artifactId gt       lt version gt some version lt  version gt       lt relativePath  gt   lt  parent gt   After changing to importing a spring pom   lt dependency gt       lt groupId gt org springframework boot lt  groupId gt       lt artifactId gt spring-boot-dependencies lt  artifactId gt       lt version gt some version lt  version gt       lt type gt pom lt  type gt       lt scope gt import lt  scope gt   lt  dependency gt   My unit tests started to run

User · Answer

Following worked just fine for me in Junit 5  https   junit org junit5 docs current user-guide  running-tests-build-maven   lt build gt       lt plugins gt           lt plugin gt               lt artifactId gt maven-surefire-plugin lt  artifactId gt               lt version gt 2 22 0 lt  version gt           lt  plugin gt           lt plugin gt               lt artifactId gt maven-failsafe-plugin lt  artifactId gt               lt version gt 2 22 0 lt  version gt           lt  plugin gt       lt  plugins gt   lt  build gt   lt  --     -- gt   lt dependencies gt       lt  --     -- gt       lt dependency gt           lt groupId gt org junit jupiter lt  groupId gt           lt artifactId gt junit-jupiter-api lt  artifactId gt           lt version gt 5 4 0 lt  version gt           lt scope gt test lt  scope gt       lt  dependency gt       lt dependency gt           lt groupId gt org junit jupiter lt  groupId gt           lt artifactId gt junit-jupiter-engine lt  artifactId gt           lt version gt 5 4 0 lt  version gt           lt scope gt test lt  scope gt       lt  dependency gt       lt  --     -- gt   lt  dependencies gt   lt  --     -- gt

User · Answer

By default Maven uses the following naming conventions when looking for tests to run    Test   Test  Tests  has been added in Maven Surefire Plugin 2 20   TestCase   If your test class doesn t follow these conventions you should rename it or configure Maven Surefire Plugin to use another pattern for test classes

User · Answer

Many of these answers were quite useful to me in the past  but I would like to add an additional scenario that has cost me some time  as it may help others in the future   Make sure that the test classes and methods are public    My problem was that I was using an automatic test class methods generation feature of my IDE  IntelliJ  and for some reason it created them as package-private  I find this to be easier to miss than one would expect

User · Answer

I faced the same issue   it resolved by below change in pom xml     lt build gt       lt testSourceDirectory gt test lt  testSourceDirectory gt         changed to     lt build gt       lt testSourceDirectory gt   project basedir  src test java lt  testSourceDirectory gt

User · Answer

Maven will not run your tests if the project has  lt packaging gt pom lt  packaging gt   You need to set the packaging to jar  or some other java artefact type  for the tests to run   lt packaging gt jar lt  packaging gt

User · Answer

UPDATE   Like  scottyseus said in the comments  starting from Maven Surefire 2 22 0 the following is sufficient    lt plugin gt       lt groupId gt org apache maven plugins lt  groupId gt       lt artifactId gt maven-surefire-plugin lt  artifactId gt       lt version gt 2 22 1 lt  version gt   lt  plugin gt      When using JUnit 5  i ran into the same problem  Maven Surefire needs a plugin to run JUnit 5 tests  Add this to our pom xml    lt plugin gt       lt groupId gt org apache maven plugins lt  groupId gt       lt artifactId gt maven-surefire-plugin lt  artifactId gt       lt version gt 2 21 0 lt  version gt       lt dependencies gt           lt dependency gt               lt groupId gt org junit platform lt  groupId gt               lt artifactId gt junit-platform-surefire-provider lt  artifactId gt               lt version gt 1 2 0-M1 lt  version gt           lt  dependency gt           lt dependency gt               lt groupId gt org junit jupiter lt  groupId gt               lt artifactId gt junit-jupiter-engine lt  artifactId gt               lt version gt 5 2 0-M1 lt  version gt           lt  dependency gt       lt  dependencies gt   lt  plugin gt    Source  https   junit org junit5 docs current user-guide  running-tests-build-maven

User · Answer

I also found that the unit test code should put under the test folder  it can not be recognized as test class if you put it under the main folder  eg   Wrong   my program src main java NotTest java   Right   my program src test java MyTest java

User · Answer

In case someone has searched and I do not solve it  I had a library for different tests    lt dependency gt           lt groupId gt org junit jupiter lt  groupId gt           lt artifactId gt junit-jupiter-api lt  artifactId gt           lt version gt   org junit jupiter version  lt  version gt           lt scope gt test lt  scope gt       lt  dependency gt    When I installed junit everything worked  I hope and help this    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

One more tip  in addition to the previous answers    In Eclipse  go to your project s Properties   click Run Debug Settings        This page allows you to manage launch configurations with the   currently selected resource    In there you can add  New     or remove  Delete  any JU  JUnit  tests you have in your project  under the src test java folder  or course

User · Answer

junitArtifactName might also be the case if the JUnit in use isn t the standard  junit junit  but for instance      lt dependency gt       lt groupId gt org eclipse orbit lt  groupId gt       lt artifactId gt org junit lt  artifactId gt       lt version gt 4 11 0 lt  version gt       lt type gt bundle lt  type gt       lt scope gt test lt  scope gt   lt  dependency gt

User · Answer

If your test class name does not follow the standard naming convention  as highlighted by  axtavt above   you need to add the pattern class name in the pom xml in order to Maven pick the test -       lt build gt       lt plugins gt           lt plugin gt               lt groupId gt org apache maven plugins lt  groupId gt               lt artifactId gt maven-surefire-plugin lt  artifactId gt               lt configuration gt                   lt includes gt                       lt include gt      UT java lt  include gt                   lt  includes gt               lt  configuration gt           lt  plugin gt       lt  plugins gt   lt  build gt

User · Answer

In my case it was adding the junit-vintage-engine which makes it compatible with older version of JUnit tests and can run them  As I m using JUnit 5    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  dependency gt

User · Answer

If you have a shared Java   Groovy application and all you have are Groovy unit tests  then Maven won t find any tests   This can be fixed by adding one unit test under src test java

User · Answer

The Maven Surefire plugin supports several test frameworks  It tries to autodetect which framework you are using  then looks for tests written using that framework  If that autodetection is confused  and chooses the wrong framework  the second stage will not find your tests  The autodetection works by scanning the classpath for the presence of significant  quot driver quot  classes for the test frameworks it supports  Therefore the autodetection can go wrong if your POM  or a depended on module  has an incorrect dependency on one of those  quot driver quot  classes  At present  2020   a particular problem is the difference between JUnit 4 and JUnit 5  The Surefire plugin treats them as different frameworks  But because of the similarity in the package names  a project can have a dependency on the wrong framework but seem OK to a casual inspection  In particular  beware that junit-platform-console is for JUnit 5  but junit-platform-runner is for JUnit 4  If your project has a dependency on the latter  Surefire will not run your JUnit 5 tests

User · Answer

If you created a Spring Boot application using Spring Initializr  tests are running all right from Intellij Idea   But  if try to run tests from a command-line   mvn clean test   You might have been surprised  that no tests were run at all  I tried to add surefire plugin with no luck  The answer was simple  pom xml contained the following dependency         lt dependency gt           lt groupId gt org springframework boot lt  groupId gt           lt artifactId gt spring-boot-starter-test lt  artifactId gt           lt scope gt test lt  scope gt           lt exclusions gt              lt exclusion gt                 lt groupId gt org junit vintage lt  groupId gt                 lt artifactId gt junit-vintage-engine lt  artifactId gt              lt  exclusion gt           lt  exclusions gt        lt  dependency gt    The exclusion  junit-vintage-engine  is dedicated for keeping backward compatibility with JUnit 4 x  So  new versions of Spring Boot Initializr do not support it by default   After I removed the exclusion  Maven started to see project s tests

User · Answer

Also  check if your test classes directory  e g  src test java  corresponds to directory listed in property  lt testSourceDirectory gt  in your pom xml under  lt build gt  property  Took me a while to find that

User · Answer

I struggle with this problem  In my case I wasn t importing the right  Test annotation   1  Check if the  Test is from org junit jupiter api Test  if you are using Junit 5    2  With Junit5 instead of  RunWith SpringRunner class   use  ExtendWith SpringExtension class   import org junit jupiter api Test    ExtendWith SpringExtension class   SpringBootTest  AutoConfigureMockMvc  TestPropertySource locations    classpath application properties       public class CotacaoTest        Test     public void testXXX

[java] Maven does not find JUnit tests to run

Examples related to java

Examples related to maven

Examples related to junit