[
http://jira.codehaus.org/browse/SUREFIRE-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter moved MSUREFIRE-163 to SUREFIRE-167:
-------------------------------------------------
Component/s: (was: Junit 4.x support)
Key: SUREFIRE-167 (was: MSUREFIRE-163)
Project: Maven Surefire (was: Maven 2.x Surefire Plugin)
> Non-Abstract TestCase not executed if name starts with Abstract
> ---------------------------------------------------------------
>
> Key: SUREFIRE-167
> URL: http://jira.codehaus.org/browse/SUREFIRE-167
> Project: Maven Surefire
> Issue Type: Bug
> Reporter: Jörg Hohwiller
>
> As a convention for src/main/java/foo/Bar.java I put the related test-case
> under src/test/java/foo/BarTest.java
> Now I discovered that for an abstract class (AbstractResourceBundle) in
> main/java the according NON ABSTRACT JUnit TestCase
> ((AbstractResourceBundleTest) was NOT executed. This changed as soon as I
> renamed it to AAbstractResourceBundleTest.
> Seems like a bug to me.
> My fist guess was that the fix for SUREFIRE-18 was made so naive but this
> seems to be not the case.
--
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
