418
votes

I am trying to package my project. But, it automatically runs the tests previous do performing the packaging. The tests insert some content in the database. This is not what I want, I need to avoid running tests while package the application. Anybody knows how run the package with out test?

21
A Unit-Test should consist of the following 4 phases: Initialization, Test, Verification and Teardown. Maybe you should adjust your tests and add an according teardown/cleanup of your database or you should use a separate database instance, not packaged with your jar file, for running your tests on.Marc-Christian Schulze
It seems that your tests are "heavy" so you don't want to execute them. But it's a bad practice. Maybe some frameworks as DBUnit may help you ? Or you can revert database changes at the end of the test?Mickael Marrache

21 Answers

706
votes

Run maven with

mvn package -Dmaven.test.skip=true
207
votes

Just provide the command mentioned below, which will ignore executing the test cases (but will compile the test code):

mvn package -DskipTests
53
votes

you can add this plugin configuration to your pom if you do not want to set command line arg:

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-surefire-plugin</artifactId>
  <configuration>
    <skipTests>true</skipTests>
  </configuration>
</plugin>
45
votes

Note that -Dmaven.test.skip prevents Maven building the test-jar artifact.

If you'd like to skip tests but create artifacts as per a normal build use:

-Dmaven.test.skip.exec
36
votes

If you are trying this in Windows Powershell, you will get this error:

[ERROR] Unknown lifecycle phase ".test.skip=true". You must specify a valid lifecycle phase or a goal in the format...

The reason for this is, in Powershell the "-" has special meaning and it is causing problem with maven.

The solution is to prepend it with a backtick (`), like so..

mvn `-Dmaven.test.skip=true install 

Reference: http://kuniganotas.wordpress.com/2011/08/12/invalid-task-test-skiptrue-you-must-specify-a-valid-lifecycle-phase/

28
votes
<properties>
    <maven.test.skip>true</maven.test.skip>
</properties>

is also a way to add in pom file

22
votes

You only have to provide

-Dmaven.test.skip

You no longer need to append =true.

19
votes

You can pass the maven.test.skip flag as a JVM argument, to skip running tests when the package phase (and the previous ones in the default lifecycle) is run:

mvn package -Dmaven.test.skip=true

You can also pass the skipTests flag alone to the mvn executable. If you want to include this information in your POM, you can create a new profile where you can configure the maven-surefire-plugin to skip tests.

19
votes

In Inllij IDEA there is an option also to skip test goal.

enter image description here

12
votes

You can add either -DskipTests or -Dmaven.test.skip=true to any mvn command for skipping tests. In your case it would be like below:

mvn package -DskipTests

OR

mvn package -Dmaven.test.skip=true
11
votes

Answering an old and accepted question here. You can add this in your pom.xml if you want to avoid passing command line argument all the time:

  <properties>
    <skipTests>true</skipTests>
  </properties>
7
votes

just mvn clean install -DskipTests

6
votes

A shorthand notation to do maven build and skip tests would be :

mvn clean install -DskipTests

5
votes

Below two commands are most useful

mvn clean package -Dmaven.test.skip=true 
mvn clean package -DskipTests

Thanks

4
votes

Tests should always[1] run before package. If you need to turn off the tests, you're doing something wrong. In other words, you're trying to solve the wrong problem. Figure out what your problem really is, and ask that question. It sounds like it's database-related.

[1] You might skip tests when you need to quickly generate an artifact for local, development use, but in general, creating an artifact should always follow a successful test run.

2
votes

For maven package without infecting maven test:

<properties>
    <maven.test.failure.ignore>true</maven.test.failure.ignore>
</properties>
1
votes

In Intellij, go to View -> Tool Windows -> choose Maven Projects. On the Lifecyle dropdown, right-click on package -> choose Create 'your-project [package]'...

Enter this value: package -Dmaven.test.skip=true -f pom.xml in the Command line field. Click Apply and a Run Configurations dropdown menu should appear along with your created custom maven command.

0
votes

You are, obviously, doing it the wrong way. Testing is an important part of pre-packaging. You shouldn't ignore or skip it, but rather do it the right way. Try changing the database to which it inserts the data(like test_db). It may take a while to set it up. And to make sure this database can be used forever, you should delete all the data by the end of tests. JUnit4 has annotations which make it easy for you. Use @Before, @After @Test annotations for the right methods. You need to spend sometime on it, but it will be worth it!

0
votes

mvn clean install -Dmaven.test.skip=true

worked for me since the -Dskip did not work anymore.

0
votes
mvn package -Dmaven.test.skip=true
-1
votes

The best and the easiest way to do it, in IntelliJ Idea in the window “Maven Project”, and just don’t click on the test button. I hope, I helped you. Have a good day :)