[
http://jira.codehaus.org/browse/SUREFIRE-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=243787#action_243787
]
Gareth Clay commented on SUREFIRE-587:
--------------------------------------
Apologies, so it is. I missed that.
I would still argue that scanning all classes is a more useful default. JUnit
imposes no restriction on test class naming, so it seems odd that surefire
filters by name by default. Wouldn't a better default be to scan all classes,
and let users impose their own restrictions if they're using a particular
naming convention? It would avoid confusion and issues like this being raised,
and I would have thought the performance hit is likely to be small on all but
very large codebases.
> Doesn't run tests if they don't end with Test
> ---------------------------------------------
>
> Key: SUREFIRE-587
> URL: http://jira.codehaus.org/browse/SUREFIRE-587
> Project: Maven Surefire
> Issue Type: Bug
> Components: JUnit 3.x support, Junit 4.x support
> Affects Versions: 2.4.3
> Environment: N/A
> Reporter: David J. M. Karlsen
> Priority: Critical
>
> We have a mix of test - some purely junit4 (e.g. not extending anything and
> annotating with @Test) - and some which extends TestCase.
> I've discovered that the ones extending TestCase won't run if the classname
> doesn't end with Test - so that the class CommonsAttributesParserTests won't
> get included (notice the ending "s").
--
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
