BUT ! :) 

instead of discussing this to death, however, using http://maven.apache.org/surefire/maven-failsafe-plugin/integration-test-mojo.html#testSourceDirectory   and putting the integration tests into something like "src/itests" is OK for me.

Much better than putting them into "src/test" or "tests" (at root level)


On Tue, May 21, 2013 at 5:30 PM, Matthias Wessendorf <matzew@apache.org> wrote:

On Tue, May 21, 2013 at 5:19 PM, Douglas Campos <qmx@qmx.me> wrote:
On Tue, May 21, 2013 at 01:50:19PM +0200, Matthias Wessendorf wrote:
> On Tue, May 21, 2013 at 1:38 PM, Kris Borchers <kris@redhat.com> wrote:
> > To me, the src directory is for just that, source, and should never be
> > cluttered with tests.
At least in Java lands, the tests are written using source code :P

> in maven, it's default that SOURCE code goes to "src/main/$LANGUAGE"; tests
> (unit tests) go to "src/test/$LANGUAGE"
Have y'all considered using maven-failsafe-plugin[1]? In this case, the
integration tests only run when you invoke mvn verify (and a name
pattern can be specified for the integration tests)


Used before - not sure, but I do not like mixing unit and integration tests, in one maven project :) 


aerogear-dev mailing list

Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf