[
https://issues.apache.org/jira/browse/SUREFIRE-530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14639576#comment-14639576
]
Tibor Digana commented on SUREFIRE-530:
---------------------------------------
Assigned to 3.0.
We will write the API documentation and my wish is to use script language to
come over building customer's artifact and simplify the use.
The problem is that plugin configuration is getting too big.
Run-order functionality needs some work to be present in configuration.
[~Tesseract] you can commit PR with a patch on GitHub and we will use it in 3.0
which will speed up our work.
> Allow runtime ordering of tests to be specified
> -----------------------------------------------
>
> Key: SUREFIRE-530
> URL: https://issues.apache.org/jira/browse/SUREFIRE-530
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Plugin
> Affects Versions: 2.4.3
> Environment: testNG, Junit
> Reporter: Nick Pellow
> Fix For: 3.0
>
>
> Allow other plugins to specify tests to get run, and preserve the ordering of
> tests.
> Currently, a plugin may set the "test" parameter with a comma separated list
> of tests to run.
> However, the order is not preserved.
> For plugins such as the maven-clover2-plugin, (possibly the
> maven-reactor-plugin?) that optimize the build/test run, ordering of a tests
> is a very nice way to ensure the build fails as fast as possible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
