[
https://issues.apache.org/jira/browse/SUREFIRE-530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14636971#comment-14636971
]
Christian commented on SUREFIRE-530:
------------------------------------
Thanks for your quick reply and the great work on SureFire so far :-)
My original idea was just to have a parameter similar to {{excludes}} and
{{includes}}:
{code}
<order>
<orderItem>ExampleATest</orderItem>
<orderItem>ExampleCTest</orderItem>
<orderItem>ExampleBTest</orderItem>
<orderItem>ExampleDTest</orderItem>
</order>
{code}
In terms of an API, I assume you want the API user to be able to configure and
trigger surefire as well as getting the results of the test run, right? In this
case, I think it would be nice, to be able, to somehow pass a list of tests,
that are run with respect to the given order. Since I have only a vague idea of
what you want to achieve, I find it difficult to be more specific.
Regarding the _s1_ branch: I spend the last two days digging into SureFire's
architecture, but I do not really have an overview yet. Thus, I cannot easily
see, what you are doing in the s1 branch. Can you maybe point out the API
relevant files and how you intend your API to be called?
> 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)
