Repository navigation
Platform Console: 0 tests found with junit-platform-console-standalone-6.1.0.jar #5761
|
I'm attempting to run a demo unit test from the command line using Platform Console 6 (junit-platform-console-standalone-6.1.0.jar). No Maven, no IDE. The test file, TestSimple.java, is attached. Just a single test with a single assertion. The platform console jar is in the same folder as TestSimple.java. I compile it as follows: javac -cp junit-platform-console-standalone-6.1.0.jar TestSimple.java Then attempt to discover the test inside the compiled class file: java -jar junit-platform-console-standalone-6.1.0.jar discover --select-file TestClass.class But the output doesn't find the test. It only finds three containers (Platform Suite, Jupiter and Vintage): 
I'm guessing that I'm missing something really obvious and would appreciate any hint as to what that is. Thanks! |
Replies: 1 comment 2 replies
The Which leads to the second item, the compiled test class is not included in the classpath. You'd add it the usual way using |
|
Thanks! That was part of my problem. The other, embarrassingly, was that I hadn't made sure that the filename (TestSimple.java) and classname were the same, so I was looking for the wrong compiled class file name (myClass.class) Doh! java -cp "." -jar junit-platform-console-standalone-6.1.0.jar execute --class-path "." --select-class myClass Thanks for the help! 
|
|
Using both |
The
--select-fileoption is a request from the platform to a test engine to discover tests in the selected file, but only if it is able too. The Jupiter, Vintage and Suite engines, included in the standalone artifact, can only discover tests on the classpath. So you'd have to use--select-classinstead.Which leads to the second item, the compiled test class is not included in the classpath. You'd add it the usual way using
java --class-path ...or by using the--class-pathoption from the console launcher.