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 default, so building doesn't run
ITs - a developer runs ITs on demand, but the CI system schedules them
every couple of hours or less, so they are frequently run.
cheers,
Christian.
On 8-Aug-08, at 10:57 , Brian E. Fox wrote:
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 and let CI do them
other
times (in case I forget on commit, or there is some other integration
issue not present on my machine)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
