[
https://jira.codehaus.org/browse/SUREFIRE-891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giorgio Vespucci closed SUREFIRE-891.
-------------------------------------
Resolution: Not A Bug
Reading again and better "Inclusions and Exclusions of Tests" and "Using JUnit"
I got that the naming convention has to be followed to include tests that have
to run; the provider does indicate how test classes are implemented, with
inheritnce a-la JUnit3 or with annotations a-la JUnit4.
> Surefire with does not pick up test classes whose name doesn't end with "Test"
> ------------------------------------------------------------------------------
>
> Key: SUREFIRE-891
> URL: https://jira.codehaus.org/browse/SUREFIRE-891
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support, Maven Surefire Plugin
> Affects Versions: 2.12
> Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
> Java version: 1.7.0_03, vendor: Oracle Corporation
> OS name: "windows 7", version: "6.1", arch: "x86", family: "windows"
> JUnit 4.10 + surefire-junit47 provider + parallel "methods"
> Reporter: Giorgio Vespucci
> Attachments: pom-surefire-issue.xml
>
>
> I followed the guide at
> http://maven.apache.org/plugins/maven-surefire-plugin/examples/junit.html but
> a couple of test classes whose name don't end with "Test", only having
> methods annotated as @Test, are not picked up and executed. These classes are
> executed normally when I class "Run as JUnit Test" in Eclipse Juno.
> A snippet of the pom.xml I'm using is attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
