Community
Participate
Working Groups
Created attachment 279367 [details] Junit run configuration error message When setting up a Junit 4 run configuration in Eclipse for my Java/Kotlin project, Eclipse UI says that "Can not find test class 'test.KotlinTestsRunner' in project 'Kgt-4' even though the 'test.KotlinTestsRunner' class is where it's supposed to be and the run configuration dependencies have been properly set up (see the enclosed pics). $ ls -l Kgt-4/build/classes/kotlin/test/test/KotlinTestsRunner.class -rw-r--r-- 1 luser luser 762 Jul 21 13:02 Kgt-4/build/classes/kotlin/test/test/KotlinTestsRunner.class
Created attachment 279368 [details] Junit run configuration dependencies
Just to clarify, 'test.KotlinTestsRunner' class is a Kotlin class that runs the project's Kotlin tests. The project also has some Java tests that are run using 'test.JavaTestsRunner' class and Junit run configuration has no problem seeing/finding and running Java tests (see attachment 3 [details]).
Created attachment 279369 [details] Junit run configuration for Java test class (notice that there is NO ERROR here) (notice that there is NO ERROR here for Java test class)
$ ls -l Kgt-4/build/classes/java/test/test/JavaTestsRunner.class -rw-r--r-- 1 luser luser 666 Jul 21 13:02 Kgt-4/build/classes/java/test/test/JavaTestsRunner.class
Created attachment 279375 [details] Java application run configuration for Kotlin tests, runs without issues
More info: If I create a Java Application run configuration (see attachment 4 [details] above) with the same Dependencies as shown in the attachment 2 [details] above it has no problems finding and running the test.KotlinTests class.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
