[ 
https://jira.codehaus.org/browse/SUREFIRE-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark Ziesemer updated SUREFIRE-844:
-----------------------------------

    Attachment: SUREFIRE-844-2.12.txt

Debug output from "mvn clean test" on the attached test project, using Surefire 
plugin version 2.12 as attached.  Observe the "No tests were executed!" 
exception.
                
> "test" parameter no longer working with JUnit in 2.12 (worked in 2.9 - 2.11)
> ----------------------------------------------------------------------------
>
>                 Key: SUREFIRE-844
>                 URL: https://jira.codehaus.org/browse/SUREFIRE-844
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Junit 4.x support
>    Affects Versions: 2.12
>         Environment: JDK 1.7.0_02, Windows 7.
>            Reporter: Mark Ziesemer
>         Attachments: SUREFIRE-844-2.11.txt, SUREFIRE-844-2.12.txt, 
> SUREFIRE-844.zip
>
>
> Maven is configured with JUnit 4.10.  Assume a 'MyTest' class with public, 
> non-static, 0-arg methods annotated with org.junit.Test.
> This was working with Surefire 2.9, 2.10, and 2.11 (and probably earlier):
>       <plugin>
>               <groupId>org.apache.maven.plugins</groupId>
>               <artifactId>maven-surefire-plugin</artifactId>
>               <version>2.11</version>
>               <configuration>
>                       <test>com.example.MyTest</test>
>               </configuration>
>       </plugin>
> With only updating the Surefire version from 2.11 to 2.12, the tests no 
> longer execute:
>       -------------------------------------------------------
>        T E S T S
>       -------------------------------------------------------
>       
>       Results :
>       
>       Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> I don't see anything in the release announcement that should account for this.
> If I remove the 'test' parameter entirely, it will again successfully run - 
> but will run all tests that it finds instead of what I'm expecting it to run.
> I can't attach any additional details from what I'm currently working on, but 
> will work on providing a proper minimal test case over the weekend.

--
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

        

Reply via email to