Tibor Digana

Hi @DaGeRe , The JIRA is not well suited to read code patches. We can discuss the code even if the CI would fail.

@DaGeRe If we want to `test our documentation`, we should use the pattern which would filter only some executions of parameterized test. Example `mvn test -Dtest=*ExampleTestJUnit4#testMethod[5:*]` and the IT allows...

Hi @winglam What's up? I checked your commit. I have one argument to the changes in `TestListResolver`. This class is a filter and not a Comparator. It would be worth...

The `TestListResolver` does not do the trick. It is only a filter. You should not use it. The whole trick is done in every Surefire Provider implementation. So in this...

It would help you and us if you have followed these steps, in separate commits, and each step would have unit tests: 1. serialize run order config + test 2....

Of course the documentation should say that `forkCount > 1` does not guarantee the order of classes.

Maybe a hint, try to run a basic project in debug mode `mvn -X test -Dtests=xxx,yyy` and go to the folder `target/surefire`. You should see two properties files and one...

How are you @winglam? We have discussed your pull request in #169 and it seems that @aslakhellesoy would pay an attention. @winglam do you have time to participate?

@aslakhellesoy The code is not suited to rebase because this code has some issues. That's the reason why I wanted to save the spare time of @winglam and I wrote...

@winglam @aslakhellesoy See my comment https://github.com/apache/maven-surefire/pull/348#issuecomment-1022724116 and see whatever surefire provider implementation and try to find `run order` or `runOrder`. Not the `TestListResolver` as many people think. The `AbstractSurefireMojo` has...