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

[Tibor Digana (JIRA)]

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

Tibor Digana updated SUREFIRE-526:
--
Fix Version/s: (was: 3.0-RC1)

> 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
>Priority: Major
> 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  
> be set as well as Properties.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Tibor Digana (JIRA)]

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

Tibor Digana updated SUREFIRE-526:
--
Fix Version/s: 2.20

> 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, 2.20
>
>
> 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  
> be set as well as Properties.



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

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

[Tibor Digana (JIRA)]

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

Tibor Digana updated SUREFIRE-526:
--
Fix Version/s: 3.0

 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)