[ http://jira.codehaus.org/browse/MSUREFIRE-113?page=comments#action_65526 ]
Brett Porter commented on MSUREFIRE-113: ---------------------------------------- this also should be changed in the TestNG provider > When you <include> a JUnit TestSuite (with no test methods), no tests are run > ----------------------------------------------------------------------------- > > Key: MSUREFIRE-113 > URL: http://jira.codehaus.org/browse/MSUREFIRE-113 > Project: Maven 2.x Surefire Plugin > Type: Bug > Versions: 2.2 > Reporter: Dan Fabulich > Priority: Blocker > 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
