[
https://issues.apache.org/jira/browse/SUREFIRE-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16258454#comment-16258454
]
ASF GitHub Bot commented on SUREFIRE-1405:
------------------------------------------
Github user Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/169
Thx for your effort but we have to wait for this till the version 3.0.
The branch will have more merge conflicts. Please rebase this in few months
when we will be about develop 3.0.
> Allow provider to override default runOrder & RunOrderCalculator from
> surefire-api
> ----------------------------------------------------------------------------------
>
> Key: SUREFIRE-1405
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1405
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Plugin
> Reporter: Dipak Pawar
> Labels: features
> Fix For: Backlog
>
>
> * Currently surefire supports "alphabetical", "reversealphabetical",
> "random", "hourly", "failedfirst", "balanced" and "filesystem" runOrder.
> * All supported options are hardCoded in RunOrder -
> https://github.com/apache/maven-surefire/blob/master/surefire-api/src/main/java/org/apache/maven/surefire/util/RunOrder.java#L109
> * There is no way for user to add new runOrder in new provider implemented by
> him.
> * Allow user to override/add new runOrder & RunOrderCalculator implementaion
> so surefire-api will dynamically load all supported runOrder & decide which
> RunOrderCalculator implementation to use for ordering test classes depending
> on provided runOrders.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
