Tibor17 edited a comment on pull request #348: URL: https://github.com/apache/maven-surefire/pull/348#issuecomment-1022747001
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 jar file. Open one property file and you should see CSV of what you have used in `-Dtest=`. This is your data. Iterate over this parse each substring, create an instance of `TestListResolver` and pickup the class/method pairs. Order them and use them as necesary in the run order calculator within the provider(s), see the `ProviderParameters#getTestRequest()`. Regarding the sanity check, go to the `AbstractSurefireMojo` class and see the parameters checkers in the `execute()` method. There are more like this. I think you should write a check that the new enum requires the test list but do not use `getTests()` directly. We are merging several config parameters together and we will change this part of code in #440 so my advice is to focus on this a bit later or check the #440 . -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
