I give those surefire issues a try and push it if it looks good. LieGrue, strub
----- Original Message ----- > From: Dan Allen <[email protected]> > To: [email protected] > Cc: > Sent: Saturday, December 24, 2011 12:14 AM > Subject: Re: basic decisions: test setup > > On Fri, Dec 23, 2011 at 13:09, Gerhard Petracek > <[email protected]>wrote: > >> i would suggest that we start with an approach which is available right >> now and to refactor the tests later on (as soon as the mentioned approach >> is available in arquillian). >> > > Speaking to that approach, you'll be happy to learn about some developments > in surefire that will make that simpler. According to Aslak: > > Surefire 2.11 got support for JUnit Categories, so you >> can configure this as filters on the surefire execution > > >> groups=EE6_FullProfile >> exludeGroups=EE6_WebProfile > > >> In talks with Ondrej we have reported to feature requests on it, > > >> http://jira.codehaus.org/browse/SUREFIRE-808 >> http://jira.codehaus.org/browse/SUREFIRE-809 > > > > Basically allowing boolean expressions in the groups/excludeGroups >> So you can say, groups=EJB&&(Security||Remote) > > >> You no longer have to make your own Categories suites like we do >> in weld-core tests, but rather surefire makes them 'on the fly' > > > I'll be excited to get something that feels more natural in Arquillian, > though. Then we should be able to switch to it rather easily. So categories > is definitely the right way to start it seems. > > -Dan > > -- > Dan Allen > Principal Software Engineer, Red Hat | Author of Seam in Action > Registered Linux User #231597 > > http://google.com/profiles/dan.j.allen > http://mojavelinux.com > http://mojavelinux.com/seaminaction >
