On Fri, Mar 11, 2016 at 2:08 PM, Stefan Egli <[email protected]> wrote: > ...Alternatively we could use the @Category junit annotation and exclude them > by default via an 'excludedGroups' via surefire
I'm not sure if that works with JUnit 3 style tests, but maybe all the affected tests are JUnit 4 anyway, I haven't checked. We have used those categories before, svn.apache.org/r1538994 - that worked well. > ...(and include them in the integration test phase)... No, we need more granularity than that. I think we can get a 10-15 minutes full build while keeping most of our integration tests active, we just need to optionally disable a few problematic tests which can be either unit or integration tests (*). Or maybe reduce them to run less testing cycles where that's possible, and run all cycles based on a specific profile. -Bertrand (*) but might need to be renamed to IT to make it clearer that they take a long time - that's a different concern
