[
https://issues.apache.org/jira/browse/SUREFIRE-530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14636941#comment-14636941
]
Tibor Digana commented on SUREFIRE-530:
---------------------------------------
[~Tesseract]
Regarding surefire fix we want to write extension (programming) API to
customize surefire behavior. Can you make any suggestion about the API? This is
the branch with some starting point of the extensions based on SPI
https://github.com/apache/maven-surefire/tree/s1
Can you specify a format of test order including the API?
Since the textual order may not satisfy requirements of all communities, I
prefer soft coded API and later we can allow users type Groovy scripts.
> 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
>
> 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)
