[ http://jira.codehaus.org/browse/SUREFIRE-31?page=comments#action_80479 ] Klaus Wiederaenders commented on SUREFIRE-31: ---------------------------------------------
Hi, this is in reply to Bernd's comment from 29/Jul/06 01:49 PM: > The problem is now that surefire's reporting classes expect information > which is not provided by junit's RunListner. So no good logs/reports > can be created. I'm not sure what information surefire's reporting classes need. However I made an XMLListener extending RunListener for JUnit 4 which produces (almost) the same output as the maven surefire XML for JUnit 3. Good reports. wiedkla > support junit 4.0 > ----------------- > > Key: SUREFIRE-31 > URL: http://jira.codehaus.org/browse/SUREFIRE-31 > Project: surefire > Issue Type: Improvement > Components: Junit 4.x support > Reporter: John Didion > Fix For: 2.1 > > Attachments: SUREFIRE-31-maven-surefire-plugin.patch, > SUREFIRE-31-surefire-trunk.patch, surefire-junit4.zip, > SUREFIRE31_karl_maven-surefire-plugin.patch, > SUREFIRE31_karl_surefire_surefire-providers_surefire-junit.patch, > SUREFIRE31_karl_surefire_surefire-providers_surefire-junit_2ndMethod.patch > > > I know this is a pretty sizable task. I just wanted to get it in the system > now that 4.0 has officially been released. Hopefully this will generate some > discussion about how 4.0 will be handled - mainly if it will require a > completely seperate implemenation of surefire (keeping the same API so it can > easily be used by the maven plugin), or if use of 4.0 will be made a > configurable option of the current surefire. > Here's some additional features I'd like to see: > 1. Ability to categorize tests. Unfortunately, 4.0 doesn't include an > @Category annotation, or make category a parameter of @Test. However, the > filtering mechanism provided by 4.0 is sufficent to support categories given > the presense of such an annotation. I recommend putting the @Category > annotation in a seperate module (surefire-annotations?) and build support for > it into surefire. Hopefully the junit guys could be convinced to incorporate > it in a later version. > 2. Similarly, support repeated tests via an @Repeated annotation. I'm not > sure how easy this would be to do external to junit. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
