[
http://jira.codehaus.org/browse/SUREFIRE-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155351#action_155351
]
Gin-Ting Chen commented on SUREFIRE-522:
----------------------------------------
When using JUnit 4 or TestNG it should not run *any* tests that are not marked
as @Test
Regardless of naming pattern.
That is specified in both the JUnit4 and TestNG docs.
Therefore if I have ParentTest that should not be run since if it is not marked
as @Test
> Classes located in src/test/java are treated as JUnit tests if they contain
> the name Test
> -----------------------------------------------------------------------------------------
>
> Key: SUREFIRE-522
> URL: http://jira.codehaus.org/browse/SUREFIRE-522
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.4.3
> Environment: Ubuntu
> Reporter: Kristoffer Moum
>
> Having recently upgradet to 2.4.3 I realise that all classes whose name
> conforms to the above described pattern are being treated as JUnit test
> classes, meaning that if the class isnt scoped public, it does not provide a
> default construct and it does not contain a test method, it will be reported
> as containing failed tests, i.e.:
> Tests in error:
> initializationError0(com.mycompany...TestMethodConfiguration)
> initializationError1(com.mycompany...TestMethodConfiguration)
> Tests run: 246, Failures: 0, Errors: 2, Skipped: 0
> The methods initializationError0 and 1 do not exist in the class obviously.
> Surefire didn't use to treat classes based on naming conventions unless the
> class name ended with "Test".
--
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
