[aerogear-dev] Integration test execution policy on Aerogear

[Daniel Bevenius]

+1 for option 3


On 25 July 2013 16:53, Matthias Wessendorf <matzew at apache.org> wrote:

>
>
>
> On Sun, Jul 14, 2013 at 4:23 AM, Douglas Campos <qmx at 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
>>
>
> +1 on option 3)
>
>
>
>>
>> > 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 at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20130725/50218a6f/attachment.html