You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Arseniy Alekseyev (JIRA)" <ji...@codehaus.org> on 2010/11/09 13:29:03 UTC

[jira] Commented: (SUREFIRE-535) surefire tries to treat nested classes, even anonymous ones, as test classes?

    [ http://jira.codehaus.org/browse/SUREFIRE-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=242528#action_242528 ] 

Arseniy Alekseyev commented on SUREFIRE-535:
--------------------------------------------

It seems my changes should go to SUREFIRE-482 and this issue should be closed because it seems to have been fixed.

> surefire tries to treat nested classes, even anonymous ones, as test classes?
> -----------------------------------------------------------------------------
>
>                 Key: SUREFIRE-535
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-535
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: JUnit 3.x support
>    Affects Versions: 2.4.2
>            Reporter: Benson Margulies
>         Attachments: patch.txt, patch.txt
>
>
> Given a top-level test class that inherits from TestCase.
> If it, internally, declares an anonymous class, or even a named child class, surefire + junit tries to run it, and fails with a warning or an initializationError. This does not happen from the vanilla junit test runner.

-- 
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