Hi, Coming back to this topic, I'd like to go ahead with the Junit @Category variant and would thus suggest to introduce a 'Slow' category marker interface to the sling.commons.testing bundle, which would be excluded from surefire/failsafe by default (via excludedGroups) - probably in the parent/pom ?
There are then various ways of how to enable/disable this Slow category, but one simple approach would be to introduce a new profile eg 'includeSlowTests' which fiddles with this excludedGroups eg via properties. We should also ensure that the Slow tests are nevertheless run when you do a release.. (no cheating) I've implemented the category/profile variant for infamously slow discovery, which would bring down the total from ca 39min down to ca 8min. A patch with the suggested change (except parent/pom changes..) is in SLING-5598 - pls let me know what you think. Unless there's -1 I'd at least introduce the category to sling.commons.testing and use it in discovery - doing this in general for all Sling bundles, ie in the parent/pom, could be perhaps done in a separate step. Cheers, Stefan -- https://issues.apache.org/jira/browse/SLING-5598 On 11/03/16 16:49, "Bertrand Delacretaz" <[email protected]> wrote: >On Fri, Mar 11, 2016 at 4:40 PM, Stefan Egli <[email protected]> >wrote: >> We could try to overwrite PaxExam as suggested in >> https://vzurczak.wordpress.com/2015/01/19/skip-tests-with-pax-exam/ .. > >Don't we use different versions of that runner in places, 3.x and 4.x ? > >After a quick search for "Category" at [1] I think JUnit categories >should work for all runners, it looks like it's the Maven surefire and >failsafe plugin which handle them. > >And if not there's always the less elegant package or class name tricks. > >-Bertrand > >[1] >http://svn.apache.org/repos/asf/maven/surefire/trunk/surefire-providers
