I know I'm not a part of the core team here, but the two tests are
written differently, and send different signals. It's
quiteappropriate to run them on different schedules, and not least
since they're usually slower than Unit Tests. In nearly all of my
clients, they don't have ITs on by
>CI did not develop or make release for us ;) So, I think we need to be
>developer oriented and not CI oriented.
Then activate the Its in the release, that makes perfect sense. The
point is I don't need long running Its in my face on every build. I
should run them before I commit, when I release a
I also think they should be activated by default.
Olivier Lamy wrote:
Hi,
Agree with Vincent, they must be activated by default (for me it tests
are similar to a junit tests).
And as we have documented in the surefire mojo : "skip ... Its use is
NOT RECOMMENDED .."
By the way I can add some ext
You're right, we have to activate them in the release process.
CI will launch them automatically every 4 hours.
IT's are often very long.
The problem we have actually (see my other thread) is that we develop too
many ITs and not enough UTs.
That's why I would prefer to have a good code coverage wit
Hi,
Agree with Vincent, they must be activated by default (for me it tests
are similar to a junit tests).
And as we have documented in the surefire mojo : "skip ... Its use is
NOT RECOMMENDED .."
By the way I can add some extra parameters during my build.
But I can forget and maybe commit somethi
2008/8/7 Benjamin Bentmann <[EMAIL PROTECTED]>:
> Hi Vincent,
>
>> Removing this activation check, ITs will never be been called by
>> default. Is it really the wanted behaviour?
>> IMHO I think unit testing implies IT testing. Does I missed something?
>
> Well, it appears to be a personal taste: I
Hi Vincent,
Removing this activation check, ITs will never be been called by
default. Is it really the wanted behaviour?
IMHO I think unit testing implies IT testing. Does I missed something?
Well, it appears to be a personal taste: I am just like you in favor of
running tests (whatever kind)
Hi Benjamin,
2008/8/7 <[EMAIL PROTECTED]>:
> Author: bentmann
> Date: Thu Aug 7 10:41:00 2008
> New Revision: 683661
>
> URL: http://svn.apache.org/viewvc?rev=683661&view=rev
> Log:
> o Synced id and activation of integration-tests with core ITs
>
> Modified:
>maven/release/trunk/maven-relea