[
https://issues.apache.org/jira/browse/SUREFIRE-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167565#comment-16167565
]
Tibor Digana commented on SUREFIRE-1405:
----------------------------------------
[~dipakpawar231]
These sort of issues should be part on version 3.0. Open pull request on Github
and implement it pls.
If there is no interest, I will close this issue.
> 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: 3.0
>
>
> * 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)
