[GitHub] [maven-surefire] Tibor17 edited a comment on pull request #169: [SUREFIRE-1405] Allows user to extend RunOrder & RunOrderCalculator

[GitBox <gi...@apache.org>]

Tibor17 edited a comment on pull request #169:
URL: https://github.com/apache/maven-surefire/pull/169#issuecomment-781321856


   > @Tibor17
   > 
   > > How can you otherwise order the classes while multiple forks wants to execute the tests?
   > 
   > Ok, thanks for confirming that this is still the case for JUnit5. I am well aware of this implication from previous projects using JUnit4 but I wasn't sure the same applies to the way surefire handles JUnit5.
   > 
   > This also applies to single-fork mode (the default), right?
   
   @famod 
   This PR is excellent solution where the old implementation has got reworked using the abstraction and polymorphism which opens the Extensions API for our users to reimplement it without asking the ASF team. So this PR should not be seen as a fix nor feature for JUnit5. The Extensions API was long lasting plan for us nevertheless JUnit5 was released.
   Regarding your question about a single JVM execution, the run-order in junit may be used instead. The surefire's run-order is always used by the plugin. I do not remember what type of run-order is default but it is mentioned in the documentation for the configuration parameter.


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

For queries about this service, please contact Infrastructure at:
users@infra.apache.org