Col-E commented on issue #252: [SUREFIRE-1711] Support @ParameterizedTest for JUnit 5 test reruns URL: https://github.com/apache/maven-surefire/pull/252#issuecomment-549207446 Well, reporting still uses the method `toClassMethodName`. So as of right now reporting format should be the same as it was. This PR's changes only helps the `launcher` choose which tests to rerun. Since normal tests do not have brackets we can easily separate the normal tests from the parameterized tests by checking if the legacy name contains a `[` or `]`. Those characters will never appear in normal `@Test` legacy names. If we want to show that different runs of `@ParameterizedTest` are unique with the `[number]` there would be some extra handling. But for `@Test` reporting I do not think there will need to be a lot of changes. Before I do anything to change the report format I would like to have a minimal example of what the xml output would be for parameterized support just to be clear on the intended format.
---------------------------------------------------------------- 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: us...@infra.apache.org With regards, Apache Git Services
