[ https://jira.codehaus.org/browse/SUREFIRE-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=289646#comment-289646 ]
John Casey commented on SUREFIRE-809: ------------------------------------- In revId 1235805: Just added tests to verify the grouping expressions work both in JUnit and TestNG. The implementation for TestNG offends my design sensibilities, but I didn't have many options for injecting the group-expression matcher logic. In the end, I had to split out the group-expression support into a separate module, and handle it much the same way the testng-utils artifact is handled...injected directly into the test classpath for testng tests. There was a tad more fine tuning related to the new integration tests too, but it's pretty minor. This feature should be complete now. > Implement boolean expression to define test group to be run. > ------------------------------------------------------------ > > Key: SUREFIRE-809 > URL: https://jira.codehaus.org/browse/SUREFIRE-809 > Project: Maven Surefire > Issue Type: New Feature > Components: Junit 4.x support, TestNG support > Affects Versions: 2.11 > Reporter: Ondrej Zizka > Fix For: 2.12 > > Attachments: BooleanExpression.g, category-expression.jj > > > This is an alternative to SUREFIRE-808. > Instead of having hard-coded filtering structure combining two lists. > an expression could be parsed and evaluated for each test. > Each test would be "tagged" using > {code} > @Categories({ MyCateg1.class, MyCateg2.class, ... }) > {code} > Surefire's `group` config param would be an expression like: > {code} > <groups>( Ejb AND (CommonCriteria OR Security) ) AND NOT( Clustering )<groups> > {code} > Presence of a category of given name would be evaluated as true, absence of > it as false. > Interface inheritance would be taken into account. > This mechanism would provide unlimited possibilities of grouping tests, and > would be very beneficial for huge testuites counting thousands of tests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira