maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bernd (JIRA)" <>
Subject [jira] Commented: (SUREFIRE-31) support junit 4.0
Date Sat, 29 Jul 2006 18:50:12 GMT
    [ ] 
Bernd commented on SUREFIRE-31:

I modifed JUnitTestSet to use JUnitCore from junit4 to run
the tests directly. I thought this is a nice way to get all the
annotation stuff working (@Before, timeout=xx) and it works.
At least it runs some exemplary tests.

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. :-(

Additionally surefire's POJO approach collides with junit4.

> support junit 4.0
> -----------------
>                 Key: SUREFIRE-31
>                 URL:
>             Project: surefire
>          Issue Type: Improvement
>            Reporter: John Didion
>         Attachments:
> 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