You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org> on 2010/12/21 17:33:58 UTC
[jira] Closed: (SUREFIRE-671) surefire should not run abstract test
cases
[ http://jira.codehaus.org/browse/SUREFIRE-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Rosenvold closed SUREFIRE-671.
---------------------------------------
Resolution: Fixed
Fixed with testcase in r1051545. Stacktrace showed this was JUnit 4.x, which is the only provider with this bug.
> surefire should not run abstract test cases
> -------------------------------------------
>
> Key: SUREFIRE-671
> URL: http://jira.codehaus.org/browse/SUREFIRE-671
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 2.7
> Reporter: Alasdair Maclean
> Assignee: Kristian Rosenvold
> Priority: Minor
> Fix For: 2.7.1
>
> Attachments: abstract-test-case.zip, tests.mms.common.MyTestCase.txt
>
>
> Surefire reports a failure if an abstract test case (extending junit.framework.TestCase) with TestCase in its name contains no tests. This bug appears to have the same symptoms as issue SUREFIRE-221, but as it's so old I'm assuming a different cause
> Workaround: adding @Ignore to the abstract test case (or change the class name)
--
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