Indeed, a project can contain and run tests from different versions without problems, which allows a slow migration to JUnit 5. I explain their meaning in a post dedicated to JUnit's architecture - for now this only means that there will be no conflicts when different JUnit versions are used in the same project. class-path target/test-classes:target/classesĪs you might have noticed, JUnit 5 occupies new namespaces: org. Java -jar junit-platform-console-standalone from production code or on test libraries) you can then use it as follows: The best way to use it is to download the standalone JAR, which comes with all the required dependencies.

In case all of this is too fancy for you, try the console launcher, which lets you run the tests directly from the command line. IDEs won't run individual test methods.īut if the other approaches do not work for you, this can be an acceptable and tool independent solution. class ) and hence the new JUnit 5 tests.ĭue to the detour through JUnit 4, some features may not be supported, e.g. If you prefer, you can use the same runner directly on the JUnit 5 test classes in that case they have to be public.Įven if slightly outdated, your favorite IDE and build tool will happily run the classes annotated with ( JUnitPlatform. The interprets packages as a hierarchy so it runs all tests in all packages prefixed with org. It has to adhere to the common naming convention and must be public.

Note that the class has to be a regular JUnit 4 test class, i.e.

Install junit in eclipse