You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by GitBox <gi...@apache.org> on 2019/11/04 02:35:14 UTC

[GitHub] [maven-surefire] Tibor17 edited a comment on issue #252: [SUREFIRE-1711] Support @ParameterizedTest for JUnit 5 test reruns

Tibor17 edited a comment on issue #252: [SUREFIRE-1711] Support @ParameterizedTest for JUnit 5 test reruns
URL: https://github.com/apache/maven-surefire/pull/252#issuecomment-549208624
 
 
   ok, let's change the methodology.
   Although the provider is able to run parameterized test, run `mvn test` with real POM (without rerun) and see what happens in the test summary on the console and the XML report in `target/surefire-reports`.
   I guess you will see the same problem what @Seijan found in https://github.com/junit-team/junit5/issues/1558
   
   The problem with JUnit5 and the Adapter is that we never know what annotations are used. We only can see some strings and signatures and list of method arguments but that's basically all regarding the test method.
   

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


With regards,
Apache Git Services