You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Gregor Heine (JIRA)" <ji...@codehaus.org> on 2008/10/19 18:14:19 UTC
[jira] Commented: (SUREFIRE-167) Non-Abstract TestCase not executed
if name starts with Abstract
[ http://jira.codehaus.org/browse/SUREFIRE-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151291#action_151291 ]
Gregor Heine commented on SUREFIRE-167:
---------------------------------------
This isn't working for me. I'm using version 2.4.3 and tests beginning with Abstract (albeit not being abstract) are not run. Also explicitly adding <include>**/Abstract*Test.*</include> doesn't help.
> 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
> Components: Junit 4.x support
> Reporter: Jörg Hohwiller
> Fix For: 2.4
>
>
> 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