First preference: disabled by default, but easily enabled.
Second preference: enabled by default, but with a separate property to disable (so you can run UTs and skip ITs).
The purist in me wants to enable by default in the integration-test phase, and just run up to test or package. But the problem is that realistically it takes too long to run them before you can install an use it after a change.
I think the typical development pattern is where you code and unit test and code and unit test, you maybe write an integration test or two and run them on their own, and then before you commit you run all the integration tests. The last part is just discipline, and as long as we have CI and the release profile in place to remind the undisciplined it should be fine.
Cheers, Brett On 08/08/2008, at 7:14 AM, Arnaud HERITIER wrote:
Hi all, You noticed that we changed in plugins the behavior of ITs. We would like to have your advice : Do you want to have ITs activated by default in the plugin build ? Why ? -- .......................................................... Arnaud HERITIER .......................................................... OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .......................................................... ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ...........................................................
-- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
