Mercurial > hg > Blog
comparison content/Maven/skipping-tests.md @ 0:4cd9b65e10e4
initial import of the pelican based blog
| author | Dirk Olmes <dirk@xanthippe.ping.de> |
|---|---|
| date | Fri, 28 Jun 2013 08:48:58 +0200 |
| parents | |
| children | 1d9382b0329b |
comparison
equal
deleted
inserted
replaced
| -1:000000000000 | 0:4cd9b65e10e4 |
|---|---|
| 1 Title: Skipping test execution but not test compilation | |
| 2 Date: 2007-05-17 | |
| 3 lang: en | |
| 4 | |
| 5 In more complicated Maven builds you might package your tests along with your normal code to use in other modules (see plugin doc to the [maven-jar-plugin](http://maven.apache.org/plugins/maven-jar-plugin/index.html) how to do it). For normal development you might not want to execute the unit tests every time you build. Compiling the source with | |
| 6 | |
| 7 mvn compile | |
| 8 | |
| 9 won't build the tests which might fail the whole build as other modules depend on the compiled test classes. So you might be tempted to use | |
| 10 | |
| 11 mvn compile test-compile | |
| 12 | |
| 13 which won't do the job either because the tests won't be compiled. At first glance using | |
| 14 | |
| 15 mvn -Dmaven.test.skip=true test | |
| 16 | |
| 17 seems to be what you want to do but alas, the tests won't be compiled in this case either. The solution to this problem is to use | |
| 18 | |
| 19 mvn -Dmaven.test.skip.exec=true test | |
| 20 | |
| 21 which actually enters the test phase (which in turn compiles the tests) but skips only the execution of the unit tests. |