[jira] Updated: (SUREFIRE-107) Odd Filename/inner class dependant behavior (and some junit tests)

["Brett Porter (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/SUREFIRE-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated SUREFIRE-107:
----------------------------------

    Fix Version/s:     (was: 2.3)
                   2.4

> Odd Filename/inner class dependant behavior (and some junit tests)
> ------------------------------------------------------------------
>
>                 Key: SUREFIRE-107
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-107
>             Project: Maven Surefire
>          Issue Type: Bug
>    Affects Versions: 2.0 (2.2 plugin)
>            Reporter: Bryce Nordgren
>            Priority: Minor
>             Fix For: 2.4
>
>         Attachments: surefire-junit-tests.patch
>
>
> I started this because I couldn't get maven 2 to recognize the tests which came with Jakarta commons-events.  The problem boils down to the fact that there are many files/classes which implement tests, but they are all collated by a single TestSuite, called AllTestSuite.java, which extends TestCase.  I am able to make maven run the tests merely by renaming this file to AllSuiteTest.java, and no other changes. 
> I tried adding an {{<include>}} element with the original name, but this did not pick up the tests.  Surefire reliably reports that there are no tests to run.
> I did some remedial testing with junit tests (coded against the surefire-junit trunk).  I was unable to reproduce this behavior, but I did uncover wierd behavior with TestCases as inner classes.  The patch against surefire-junit trunk is included and includes only minor changes to the POM and the tests I wrote.

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