[GitHub] marcphilipp commented on issue #183: junit5

[GitBox <gi...@apache.org>]

marcphilipp commented on issue #183: junit5
URL: https://github.com/apache/maven-surefire/pull/183#issuecomment-381411134
 
 
   > I want to understand the old commit of IT junit4/pom.xml . Why we have two profiles junit5-jupiter and junit5-vintage? They are the same.
   
   The profiles are similar but not the same. While the former adds junit-jupiter-engine as a dependency, the latter adds junit-vintage-engine.
   
   > Why we have direct dependencies of junit-platform-launcher, junit-platform-engine with scope=compile. Why there is not provided scope like it is in TestNG provider in Surefire?
   
   Users of Surefire/Jupiter only need junit-jupiter-api in their POM's dependencies (scope=test) in order to write tests. At runtime, they need junit-jupiter-engine to execute tests using the new provider (as added by the `junit5-jupiter` profile). The provider needs junit-platform-launcher and its dependency junit-platform-engine because it references classes from both artifacts in its code. You can think of the Launcher API as a replacement of `JUnitCore` from JUnit 4. These are usually not added/provided by the users manually.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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