You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tibor Digana (JIRA)" <ji...@apache.org> on 2015/06/10 04:32:00 UTC

[jira] [Commented] (SUREFIRE-526) Better support for other plugins to determine which tests are included/excluded and the order the tests get run

    [ https://issues.apache.org/jira/browse/SUREFIRE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14579881#comment-14579881 ] 

Tibor Digana commented on SUREFIRE-526:
---------------------------------------

To excludes a single test just use:
-Dtest=!TestToExclude
available in 2.19.

> Better support for other plugins to determine which tests are included/excluded and the order the tests get run
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: SUREFIRE-526
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-526
>             Project: Maven Surefire
>          Issue Type: Improvement
>          Components: Maven Surefire Plugin
>            Reporter: Nick Pellow
>             Fix For: 3.0
>
>
> Currently, it is possible to provide the 'test' pattern to the maven-surefire-plugin to include/exclude specific tests to be run.
> This can be set on the MavenProject instance of any plugin which runs prior to the surefire plugin.
> Since this is just a pattern of tests to include, it has the following shortcomings:
> * To excludes a single test, you need to add _all_ tests, minus the test to exclude
> * The order of the test patterns is not used when the tests get run.
> If there is no better means to control which tests get run and in which order from outside the surefire plugin, how do you suggest this be achieved? 
> This may require changes to maven core to allow attributes <String,Objects> be set as well as Properties.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)