maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Gilday (JIRA)" <>
Subject [jira] Commented: (SUREFIRE-31) support junit 4.0
Date Mon, 04 Dec 2006 11:20:57 GMT
    [ ] 
Martin Gilday commented on SUREFIRE-31:

Is anything "official" being worked on for this at the moment?  It seems to be blocking many
people from migrating to JUnit 4.  I too am considering using TestNG now instead.

> support junit 4.0
> -----------------
>                 Key: SUREFIRE-31
>                 URL:
>             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,, SUREFIRE31_karl_maven-surefire-plugin.patch, SUREFIRE31_karl_surefire_surefire-providers_surefire-junit.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
> 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:
For more information on JIRA, see:


View raw message