Hi, On Thu, Jul 2, 2009 at 15:00, Jukka Zitting<[email protected]> wrote: > Hi, > > I'd like to introduce a separate jackrabbit-it component where we > could put any long-running integration tests that don't need to be run > per each commit. This component would be included in the build only > when a special "it" profile is enabled. > > Hudson would be configured to always include these integration tests > and they would also be a mandatory part of the release process.
+1 I like the idea. if something is wrong we still get failure emails. I think that's fine. > The big question is of course whether we should move the TCK tests > away from the default build to the integration tests. Currently the > TCK takes about 75 seconds on my desktop and the default build runs it > twice, once for core and once for spi2jcr. I'd rather keep them for jackrabbit-core, but I agree the quicker the better. We could try to parallelize the tests. but I don't know if that's easily possible with JUnit and our test setup. regards marcel
