Tibor17 edited a comment on pull request #488: URL: https://github.com/apache/maven-surefire/pull/488#issuecomment-1072734036
@nhojpatrick The entries cannot be reordered as you like. First the order is defined by the configuration and the XML reporter respects the execution order by `runOrder`. All the inclusions and exclusions config params have nothing to do with the test order. Second, it does not make sense to do anything about `TestSetRunListener` and `StatelessXmlReporter` like this because the purpose according to the roadmap is make a refactoring exactly of these entries. That's the reason why we have a new property `testRunId` in `ReportEntry` because it is the prereq of the refactoring. If we apply this, we would again spend the time to analyse what custom requirements have been done, evaluate what they broke, etc. etc. etc. Regarding the run order, there is #348 we discussed yesterday. There are people from the Illinios University like Winglam and Professor Jonathan Bell who has helped us with several other features. If you still think that the order of tests in the XML should be ordered other way than `runOrder`, you should follow `StatelessReportMojoConfiguration`, but still the PRs like this would complicate refactoring and it is much safer to make the refactoring first, then use builder for the `StatelessXmlReporter` constructor, and then apply the customer features. -- 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]
