You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "nkeywal (JIRA)" <ji...@codehaus.org> on 2011/12/09 18:13:41 UTC

[jira] Commented: (SUREFIRE-806) Make ignoring of and on -Dtest=... optional (for multiple Surefire executions)

    [ https://jira.codehaus.org/browse/SUREFIRE-806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285351#comment-285351 ] 

nkeywal commented on SUREFIRE-806:
----------------------------------

Note that you have the same issues when playing with categories.


> Make ignoring of <includes> and <excludes> on -Dtest=... optional (for multiple Surefire executions)
> ----------------------------------------------------------------------------------------------------
>
>                 Key: SUREFIRE-806
>                 URL: https://jira.codehaus.org/browse/SUREFIRE-806
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Maven Surefire Plugin
>    Affects Versions: 2.11
>            Reporter: Ondrej Zizka
>         Attachments: surefire-806-testParam-hits-all-executions.zip
>
>
> Let's have a single module with multiple Surefire executions (e.g. with different Arquillian configs)
> Tests are divided to run in either one, using <includes> and <excludes>.
> Then, if you use -Dtest=..., the specified test(s) is run twice - once for each execution (and usually fails in one of them in our scenario).
> My suggestion is to introduce a Surefire config property which would make this behavior optional:
> {code}
> <configuration>
>   <ignoreIncludesOnSingleTest>false</ignoreIncludesOnSingleTest>
> </configuration>
> {code}
> This would cause Surefire to run the intersection of the two sets -
> one created by the mask from -Dtest=...,
> second created by the includes and excludes of the respective execution.
> Current description from http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html :
> {quote}
> Specify this parameter to run individual tests by file name, overriding the includes/excludes parameters. Each pattern you specify here will be used to create an include pattern formatted like **/${test}.java, so you can just type "-Dtest=MyTest" to run a single test called "foo/MyTest.java".
> This parameter overrides the includes/excludes parameters, and the TestNG suiteXmlFiles parameter.
> {quote}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira