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

Brett Porter moved MSUREFIRE-113 to SUREFIRE-120:
-------------------------------------------------

    Affects Version/s:     (was: 2.0 (2.2 plugin))
                       2.0 (2.2 plugin)
        Fix Version/s:     (was: 2.3)
                       2.3
                  Key: SUREFIRE-120  (was: MSUREFIRE-113)
              Project: Maven Surefire  (was: Maven 2.x Surefire Plugin)

> When you <include> a JUnit TestSuite (with no test methods), no tests are run
> -----------------------------------------------------------------------------
>
>                 Key: SUREFIRE-120
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-120
>             Project: Maven Surefire
>          Issue Type: Bug
>    Affects Versions: 2.0 (2.2 plugin)
>            Reporter: Dan Fabulich
>         Assigned To: Mike Perham
>            Priority: Blocker
>             Fix For: 2.3
>
>         Attachments: MSUREFIRE-113.patch, suitebug.zip, 
> surefire-junit-2.1-SNAPSHOT.jar
>
>
> In the attached Maven project, I started with the default Maven getting 
> started archetype and then created an AppTestSuite class, which extends 
> TestSuite and defines the static suite() method, but it has no test methods 
> of its own.  Then I added an <includes> configuration that specified 
> <includes><include>**/AppTestSuite.java</include></includes>.  But when I run 
> "mvn test", it claims that "There are no tests to run."
> I've watched this happening in a debugger.  The problem is in 
> surefire-api-2.0.jar in PojoTestSet , on line 249.  When attempting to 
> acquire a list of the number of tests to run, instead of invoking the suite 
> method and counting the number of tests that come out, it's attempting to 
> discoverTestMethods on the object (methods whose names begin with "test*"), 
> which naturally won't work for suites.
> This is a really serious issue that's going to block testing for us.  (We 
> happen to attach a TestSetup decorator to our suite, so we do need to run 
> these tests as a suite rather than as individual test cases.)

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

        

Reply via email to