[ 
https://issues.apache.org/jira/browse/SUREFIRE-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16258921#comment-16258921
 ] 

ASF GitHub Bot commented on SUREFIRE-1405:
------------------------------------------

Github user dipak-pawar commented on the issue:

    https://github.com/apache/maven-surefire/pull/169
  
    Sure, we will be happy to move it forward. Please keep this PR open and let 
us know by commenting here when it will make sense to resume the effort. I 
really hope we can make it upstream. 


> 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)

Reply via email to