olamy commented on PR #169: URL: https://github.com/apache/maven-surefire/pull/169#issuecomment-6575710367
Hi @dipak-pawar, thanks a lot for this PR, and sorry it sat here for so long. I had another look against current master. The problem is still real: RunOrder is still a fixed list, and you can't plug in your own RunOrderCalculator. But the code has moved on a lot since 2017: - the packages were renamed - the JUnit 3/4 and TestNG providers are gone (everything runs on the JUnit Platform now) - hourly was removed - random ordering now uses a seed So this branch can't really be rebased anymore. On top of that, on the JUnit Platform the run order now partly goes through JUnit's own class and method orderers. A new design would have to handle that too. I'm going to close this PR, but the idea is still welcome. We'll keep tracking it in #2283. If you or anyone else wants to pick it up, a fresh PR against master would be great. Ideally the implementation would be chosen in the POM, the same way the reporter extensions work. Thanks again for the work you put into this! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
