Maven -DskipTests ignored

java maven junit maven-surefire-plugin
NeplatnyUdaj picture NeplatnyUdaj · Nov 7, 2013 · Viewed 98.7k times · Source

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?

Answer

Jack picture Jack · Nov 7, 2013

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.

Related questions

How to run JUnit tests by category in Maven?

Using JUnit 4.8 and the new @Category annotations, is there a way to choose a subset of categories to run with Maven's Surefire plugin? For example I have: @Test public void a() { } @Category(SlowTests.class) @Test public void b() { } And I'd …

Read More
Surefire is not picking up Junit 5 tests

I wrote a simple test method with JUnit 5: public class SimlpeTest { @Test @DisplayName("Some description") void methodName() { // Testing logic for subject under test } } But when I run mvn test, I got: ------------------------------------------------------- T E S T S ------------------------------------------------------- Running SimlpeTest …

Read More
Surefire Maven plugin: "Corrupted STDOUT by directly writing to native stream in forked JVM"

My JUnit tests are failing when running them through Maven and the Surefire plugin (version information below). I see the error message: Corrupted STDOUT by directly writing to native stream in forked JVM 4. See FAQ web page and the dump …

Read More