Maven -DskipTests ignored

Question

I'm building a Maven project with following SureFire configuration:

<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-surefire-plugin</artifactId>
    <version>${version.maven-surefire-plugin}</version>
    <configuration>
        <includes>
            <include>**/*Test.java</include>
        </includes>
    </configuration>
</plugin>

Problem is, that when I build it with mvn clean install -DskipTests=true, the tests are still being executed. What could be the problem?

I tried both -DskipTests(which is from the Maven website) and -DskipTests=true, which is added by IntelliJ Idea when I check "skip tests" checkbox.

I don't use any Maven settings.xml.

Maven version: 2.2.1
Surefire plugin: 2.3

EDIT If I comment out the SureFire plugin configuration, the parameter behaves as I expect to. What could be the problem with the configuration above?

farmer: EDIT: This works, but it does something different. The tests are not only disabled, but also not compiled Reimus: Same result — NeplatnyUdaj, Nov 07 '13 at 14:51
could you paste the full pom.xml and i will see if i can test it — farmer1992, Nov 07 '13 at 14:52
That surefire configuration is redundant. Surefire is always run even without explicitly configuring the plugin because it's a standard plugin. Get rid of the whole section and see what happens. — artbristol, Nov 07 '13 at 14:53
artbristol: It's a multimodule project with thousands of lines of poms. Is there something I could check? — NeplatnyUdaj, Nov 07 '13 at 14:54
en. i think you can check if `pom.xml` has a parent `pom.xml` — farmer1992, Nov 07 '13 at 14:57
Please see my edit. I think the problematic part of the pom is what I've already posted. — NeplatnyUdaj, Nov 07 '13 at 14:58
Are your tests in the standard `src/test/java` directory for each of your modules or in different locations? What is the purpose of having the section you posted in your POM? — Nicola Musatti, Nov 07 '13 at 15:00
yes, they are in the correct place. The reason for the configuration is, that I have a class TestSettings which I use for static configuration and I don't want it to be executed as a JUnit test. I only want files like ```xxxTest.java``` tested. — NeplatnyUdaj, Nov 07 '13 at 15:03
Don't you use decorations to mark which classes/methods are part of your actual test suite? — Nicola Musatti, Nov 07 '13 at 15:06
artbistol: It helped, but I don't see why. I need the configuration, because I don't like the default pattern for what is and isn't a JUnit test. Nicola Musatti: I don't know what that is so I think no. — NeplatnyUdaj, Nov 07 '13 at 15:06
@JamesB. I was using 2.3. When I upgraded to newer version it is fine. Thanks for your help. — NeplatnyUdaj, Nov 07 '13 at 15:32
Just rename `TestSettings` to something without Test in the name — artbristol, Nov 08 '13 at 14:38

score 63 · Answer 1 · edited Sep 16 '22 at 01:28

63

Maven knows two types of parameters for skipping tests:

-Dmaven.test.skip=true

or

-DskipTests=true

The surefire-plugin documentation only mentions the first one, which you have not tried yet.

edited Sep 16 '22 at 01:28

gian1200

3,670
2
30
59

answered Nov 07 '13 at 14:49

Jack

2,937
5
34
44

4

But maven.test.skip also skips compiling the tests. This is not necessarily what the OP wants. – JamesB Nov 07 '13 at 14:52
Is it possible to compile tests and just not run them? – NeplatnyUdaj Nov 07 '13 at 14:55
1

The flag you are using should do that @NeplatnyUdaj – JamesB Nov 07 '13 at 14:59
Yes. It should. Apparently my surefire plugin configuration breaks it. Please see the edit of the original post. – NeplatnyUdaj Nov 07 '13 at 15:00

Aaron Digulla · Accepted Answer · 2013-11-07T16:05:33.143

16

What you did should work. How to debug this further:

Run mvn help:effective-pom to see the whole POM that Maven will execute. Search it for test (case insensitive) to see if there is something odd.
Run mvn test -X to get debug output. This will print the options used to configure the maven-surefire-plugin. Make sure you redirect the output to a file!

In the log, you will see
```
[DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-surefire-plugin:2.15:test' with basic configurator -->
```
and then, some lines below that:
```
[DEBUG]   (s) runOrder = filesystem
[DEBUG]   (s) skip = false
[DEBUG]   (s) skipTests = false
```
These values mean that tests aren't skipped.
Are you using a recent version of the plugin? Check here. Maybe this option wasn't supported for your version.

edited Nov 07 '13 at 16:05

answered Nov 07 '13 at 15:08

Aaron Digulla

321,842
108
597
820

In step 1 I don't see anything odd, but I don't know exactly what to look for either. I see none of these parameters in step 2. these are the parameters I have(which I think could mean something in this problem): forkMode=once; childDelegation=false; parallel=false;useFile=true – NeplatnyUdaj Nov 07 '13 at 15:15
Which version of the plugin? – Aaron Digulla Nov 07 '13 at 15:16
2

Update to version 2.15. 2.3 is pretty old. Maybe it doesn't support the compact syntax. – Aaron Digulla Nov 07 '13 at 15:23
1

ahh... now I understand it. It works when I remove the surefire configuration exactly because it uses newer version otherwise. – NeplatnyUdaj Nov 07 '13 at 15:31
2

@AaronDigulla you seem to have been the first to suggest updating surefire. Why don't you post your comment as an answer so that NeplatnyUdaj can accept it? This would give you a little reputation increase and make the solution much more visible. – Nicola Musatti Nov 07 '13 at 16:03
Nicola: I was about to suggest that too :) – NeplatnyUdaj Nov 07 '13 at 16:06

score 12 · Answer 3 · edited May 21 '19 at 05:58

12

it is not -DskipTests=true it is just -DskipTests considering you are using surfire version 2.3

so you run it as

mvn install -DskipTests

edited May 21 '19 at 05:58

J. Chomel

8,193
15
41
69

answered Nov 07 '13 at 15:20

Raji

527
3
6

2

I do this all the time. But my surefire version is 2.5.. I just tried it with 2.3 surefire version and it is ignoring the skipTests. Can you tried it with 2.5? – Raji Nov 07 '13 at 15:27
1

Yes. That was the problem. It perfectly explains the behavior I observed – NeplatnyUdaj Nov 07 '13 at 15:31
both can be used -DskipTests being just more convenient – Gorky Jan 12 '17 at 21:43

score 2 · Answer 4 · answered Mar 14 '16 at 16:50

2

I'm not sure why the correct answer hasn't been posted yet. In older versions of SureFire the flag to compile tests but not run them is -Dmaven.test.skip.exec.

answered Mar 14 '16 at 16:50

Chris

5,571
2
20
32

score 2 · Answer 5 · answered Nov 26 '19 at 08:29

It's old question, but maybe my case help for someone.

So, -DskipTests/-DskipTests=true/-DskipITs/etc didn't work, and I didn't know why. I had <profiles> in my parent pom.xml and problem was in configuration of surefire/failsafe.

<profiles>
        <profile>
            <id>unit-test</id>
            <activation>
                <activeByDefault>true</activeByDefault>
            </activation>
        </profile>
        <profile>
            <id>integration-test</id>
            <properties>
                <skip.unit-tests>true</skip.unit-tests>
                <skip.integration-tests>false</skip.integration-tests>
                <skip.end-to-end-tests>true</skip.end-to-end-tests>
            </properties>
        </profile>
...
</profiles>

In plugins configuration I used like below:

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

This command didn't work:

mvn clean install -DskipTests -DskipITs

This works:

mvn clean install -Dskip.unit-tests=true -Dskip.integration-tests=true -Dskip.end-to-end-tests=true

score 0 · Answer 6 · answered Nov 07 '13 at 14:45

0

Try the following configuration for your surefire plugin

<plugin>
    <artifactId>maven-surefire-plugin</artifactId>
    <version>${version.surefire.plugin}</version>
    <configuration>
        <skip>true</skip>
    </configuration>
</plugin>

answered Nov 07 '13 at 14:45

Andrei Nicusan

4,555
1
23
36

1

Exactly. I want them to be executed on the build server and when someone checkout the code. I just need to disable them in my project configuration – NeplatnyUdaj Nov 07 '13 at 14:48
2

You can create distinct Maven build profiles for distinct scenarios in which you'd need either to skip or execute the tests – Andrei Nicusan Nov 07 '13 at 14:50
3

This seems like an overkill for such simple thing. – NeplatnyUdaj Nov 07 '13 at 14:53

Maven -DskipTests ignored

6 Answers6