I'll go for option 3 too.
To me, it's a good compromise we've got integration tests close to the code they
belong to.
And we don't interfere with development process. Travis will tell us is something go
wrong!
++
Corinne
On Jul 14, 2013, at 4:23 AM, Douglas Campos <qmx(a)qmx.me> wrote:
On Fri, Jul 12, 2013 at 03:45:21PM +0200, Karel Piwko wrote:
> 3/ Skip integration tests by default. No "container" profile is activated
by
> default, skipITs=true by default. Activate container profile in Travis and QE
> machines only.
+1, and kinda no-brainer - requiring an entire container to be available
during normal workflow is painful :P
> Would need to activate a Maven profile for test development. Travis will
> still bug developers if something fails ;-)
And this was the biggest reason I was one of those who wanted this to
always live in a separate repo ;)
--
qmx
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev