You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org> on 2011/01/02 13:58:58 UTC
[jira] Closed: (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:all-tabpanel ]
Kristian Rosenvold closed SUREFIRE-535.
---------------------------------------
Resolution: Fixed
Fix Version/s: 2.7
This issue was fixed with SUREFIRE-482. Feel free to re-open or create new issue if there still is some corner case that is not covered. Be sure to specify which provider is being used.
> 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
> Fix For: 2.7
>
> 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