Running a single test in maven -> No tests were executed

Question

When I run a single test in Maven with this command:

mvn test -Dtest=InitiateTest

I'm getting the following result:

No tests were executed!

It worked a couple of minutes ago, but now it stopped working for some reason. I tried running mvn clean a couple of times before running the test, it doesn't help.

The test looks like this:

import org.openqa.selenium.*;
import org.openqa.selenium.firefox.FirefoxDriver;
import org.openqa.selenium.support.ui.Select;
import org.junit.After;
import org.junit.Before;
import org.junit.Test;

public class InitiateTest {

    public static FirefoxDriver driver;

    @Before
        public void setUp() throws Exception {
            driver = new FirefoxDriver();
    }

    @Test
    public void initiateTest() throws Exception {
            driver.get("http://localhost:8080/login.jsp");
            ...
    }

    @After
    public void tearDown() throws Exception {
        driver.close();
    }
}

UPDATE:

It's caused by adding this dependency to POM:

<dependency>
   <groupId>org.seleniumhq.selenium</groupId>
   <artifactId>selenium</artifactId>
   <version>2.0b1</version>
   <scope>test</scope>
</dependency>

When I remove it, everything works fine. Everything works fine even when I add these two dependencies instead of the previous one:

<dependency>
   <groupId>org.seleniumhq.selenium</groupId>
   <artifactId>selenium-support</artifactId>
   <version>2.0b1</version>
   <scope>test</scope>
</dependency>
<dependency>
   <groupId>org.seleniumhq.selenium</groupId>
   <artifactId>selenium-firefox-driver</artifactId>
   <version>2.0b1</version>
   <scope>test</scope>
</dependency>

This is weird.

What kind of test are you trying to run? You did not put an @Ignore by any chance? — Navi, Jan 10 '11 at 10:59
Probably not too helpful..but remember, both those are beta products and mightily subject to breaking all over the place. — mezmo, Jan 10 '11 at 20:35

score 13 · Accepted Answer · edited Jul 18 '22 at 09:59

13

You are probably picking up JUnit3 on your classpath somewhere, which effectively disables JUnit4.

Run mvn dependency:tree to find out where it's coming in from and add exclude if from the dependency.

edited Jul 18 '22 at 09:59

Ahmad Al-Kurdi

2,248
3
23
39

answered Jan 10 '11 at 19:45

krosenvold

75,535
32
152
208

joel truher · Answer 2 · 2017-05-19T04:02:46.870

12

Perhaps you are seeing this bug, which is said to affect surefire 2.12 but not 2.11?

edited May 19 '17 at 04:02

answered Apr 26 '12 at 19:11

joel truher

742
7
18

1

Thanks, this is what I was running into. I ended up using 2.12.3 which contains a fix. – Matt Lachman Sep 07 '12 at 15:27
1

Seconded, 2.12.3 contained the fix for this. – Yinzara Mar 27 '13 at 01:48
1

Apparently also 2.19.1 carries the bug :( – Jaroslav Záruba Aug 02 '16 at 08:40
1

it helps me too, really caused by the testng conflict with selenium internal version . thanks . take to use surefire 2.19.1 ,no problem now . – Alter Hu Aug 08 '16 at 01:45
1

Link is dead and no summary in answer, so this answer is almost pointless now. – Cedric Reichenbach Sep 06 '16 at 09:18
With 2.19.1 I was able to run a single test, with 2.19 I've got the "No tests were executed!" error. – svenmeier Mar 07 '17 at 15:15
fixed the link. – joel truher May 19 '17 at 04:03

score 6 · Answer 3 · answered Jan 11 '11 at 20:23

6

I had the same problem. It was caused by testng dependency that came with junit3. Just add a exclusion statement for it and tests should work.

<dependency>
  <groupId>org.seleniumhq.selenium</groupId>
  <artifactId>selenium</artifactId>
  <version>2.0b1</version>
  <exclusions>
    <exclusion>
      <groupId>org.testng</groupId>
      <artifactId>testng</artifactId>
    </exclusion>
  </exclusions>
</dependency>

answered Jan 11 '11 at 20:23

pete

61
1

It was the same for me a minute a go... or an hour before I found this :/ THX man – yoosiba May 11 '11 at 21:39

score 4 · Answer 4 · answered Apr 30 '20 at 14:57

4

I got this error when trying to use @org.junit.Test

with

<build>
    <plugins>
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-surefire-plugin</artifactId>
            <version>2.22.2</version>
        </plugin>
    </plugins>
</build>

The correct annotation to be used is @org.junit.jupiter.api.Test

answered Apr 30 '20 at 14:57

BabaNew

884
1
13
27

wow! didn't expect this at all, and yes, the automatic imports fix makes it easy to import org.junit.Test - what is this Jupiter API anyway? :/ – hello_earth Aug 14 '20 at 08:58

score 3 · Answer 5 · answered Jun 01 '13 at 22:13

3

I have changed "maven-surefire-plugin" to 2.14.1 version (from 2.12) and it helped

answered Jun 01 '13 at 22:13

johndoe

39
1

score 1 · Answer 6 · answered Jan 23 '14 at 15:56

1

In my case, I was running a single test using mvn test -Dtest=MyTest. My mistake was that the only test had its @test annotation commented out so no test was being found in the file by junit. Doh!

answered Jan 23 '14 at 15:56

Farrukh Najmi

5,055
3
35
54

Kalpesh Soni · Answer 7 · 2019-10-03T19:07:48.907

1

changed from 2.6 to 2.18.1 and things work now

edited Oct 03 '19 at 19:07

answered Apr 21 '16 at 19:17

Kalpesh Soni

6,879
2
56
59

score 1 · Answer 8 · answered Jun 16 '16 at 13:58

1

In the build session of the pom.xml, include this:

 <build>
    <sourceDirectory>src</sourceDirectory>
    <plugins>
      <plugin>
       <groupId>org.apache.maven.plugins</groupId>
       <artifactId>maven-surefire-plugin</artifactId>
       <version>2.14.1</version>
     </plugin>
    </plugins>
  </build>

answered Jun 16 '16 at 13:58

Roberto Rodriguez

3,179
32
31

1

indeed my pom.xml was missing maven-surefire-plugin entry entirely, so I skipped the other suggestions about the plugin versions - my bad – hello_earth Jul 30 '20 at 09:59

AJC · Answer 9 · 2017-08-16T19:19:24.490

I had a similar issue. So I had to build the project from project's root level using

mvn clean install -DskipTests=True

And then run the test command from the directory where test package's pom was residing

mvn test -Dtest=TestClass

Also make sure that value of skip option is true. For example in my pom file, the default value of skip is true.

 <properties>
    <skipTests>true</skipTests>
</properties>


<build>
    <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-surefire-plugin</artifactId>
            <configuration>
                <skip>${skipTests}</skip>
            </configuration>
    </plugin>
</build>

So when I run the maven test, I set it to false

mvn test -Dtest=TestUserUpdate* -DskipTests=false

score 1 · Answer 10 · answered Nov 13 '19 at 11:43

1

update the org.apache.maven.plugins:maven-surefire-plugin to 2.22.0, it was resolved.

answered Nov 13 '19 at 11:43

user2305645

11
1

1

Welcome to StackOverflow.Please note this type of answer should be in a comment. – Pratik Bhajankar Nov 13 '19 at 11:47

score 1 · Answer 11 · answered Oct 02 '11 at 21:05

Had a similar problem adding jtestr dependency. It turns out one of its dependencies was picking up junit-3.8.1. I solved it using the exclusion statement below

<dependency>
  <groupId>org.jtestr</groupId>
  <artifactId>jtestr</artifactId>
  <exclusions>
   <exclusion>
    <groupId>org.testng</groupId>
    <artifactId>testng</artifactId>
   </exclusion>
  </exclusions>
  <version>0.6</version>
  <scope>test</scope>
</dependency>

score 0 · Answer 12 · answered Jan 10 '11 at 11:01

0

Try running maven in debug mode. It might give you more information.

mvn -X -Dtest=InitiateTest test

answered Jan 10 '11 at 11:01

dogbane

266,786
75
396
414

score 0 · Answer 13 · answered Nov 16 '20 at 19:23

I had this issue when duplicating and refactoring a test from a different class.

The issue was annotating a private method with @Test, causing it to be ignored, changing to public fixed the issue. :facepalm:

    @Test
    public void testImportOrderItems() {

score -1 · Answer 14 · answered Jan 10 '11 at 12:21

-1

Maybe as useless as my last attempt, but I just read a JUnit 4 test class should import org.junit.Test.* and org.junit.Assert.* to be considered so. As you don't have the Assert import, it might be worth trying this quickly just to be sure...

answered Jan 10 '11 at 12:21

blaguman

1
1

score -2 · Answer 15 · edited Mar 21 '17 at 19:20

-2

mvn test -Dtest='xxxx.*Test' -Dmaven.test.failure.ignore=true  -DfailIfNoTests=false

I have meet the same question that No tests were executed! My suggestion is add another paramters that -Dmaven.test.failure.ignore=true -DfailIfNoTests=false can solve it.

edited Mar 21 '17 at 19:20

Petter Friberg

21,252
9
60
109

answered Mar 21 '17 at 02:33

user7743084

9

3

Ensuring that the error is not ignored does absolutely nothing to prevent the error from occurring. – Matthew Read Sep 24 '17 at 20:32

score -3 · Answer 16 · answered Jan 10 '11 at 11:04

-3

I don't really how the @Test annotation processes your test, but can you try prefixing your test method with "test"?

public void testInit() throws Exception {
      driver.get("http://localhost:8080/login.jsp");
      ...
}

answered Jan 10 '11 at 11:04

blaguman

1
1

@Test annotation was introduced in jUnit 4, in jUnit 3 every method had to start with "test" – Kennet Jan 10 '11 at 11:13
yep, that unfortunately doesn't help. @Test annotation is enough. – John Manak Jan 10 '11 at 11:48

Running a single test in maven -> No tests were executed

16 Answers16

Linked