[
http://jira.codehaus.org/browse/SUREFIRE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=246165#action_246165
]
Kristian Rosenvold commented on SUREFIRE-424:
---------------------------------------------
This issue is fixed for junit 4.x, probably still open for 3.x
> A class providing JUnit's suite() method need not itself implement Test. But
> Surefire ignores the suite if it doesn't.
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: SUREFIRE-424
> URL: http://jira.codehaus.org/browse/SUREFIRE-424
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.4
> Reporter: Andreas Krüger
> Priority: Minor
> Fix For: Backlog
>
>
> Often, there is one test method per test case. JUnit allows a test class to
> be more flexible: It may generate a test suite at test run time, which may
> contain any number of tests.
> JUnit has traditionally required
> * a {{public static suite()}} method
> * returning {{junit.framework.Test}} (or some type, such as {{TestSuite}},
> that can be cast to {{Test}} ).
> In addition to these JUnit requirements, Surefire imposes one more
> requirement:
> * the class that contains the {{suite()}} method needs to itself implement
> {{junit.framework.Test}} .
> If that additional requirement is not met, the {{suite()}} method is not
> called, but silently ignored.
> Surefire should not impose this additional requirement, but call any
> {{suite()}} method that returns something that can be cast to
> {{junit.framework.Test}} , in any test class.
--
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
