Bug 553606 - Shortcut for JUnit doesn't work on Kotlin class
Summary: Shortcut for JUnit doesn't work on Kotlin class
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.13   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-29 02:56 EST by Arnošt Havelka CLA
Modified: 2023-11-10 04:47 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arnošt Havelka CLA 2019-11-29 02:56:16 EST
I'm not quite sure where to report this bug. So point me to better place the bug is not relevant here.

I created fresh new SpringApplication (https://start.spring.io/) with:
1. no extra dependency
2. version 2.2.1
3. Kotlin language
4. Maven build

Then I prepared my environment as:
1. downloaded eclipse-jee-2019-09-R-win32-x86_64.zip
2. create new workspace
3. installed OpenJDK 11.0.4
4. installed Kotlin plugin 0.8.19

When I tried to run JUnit test (or my own test) with shortcut "ALT+SHIFT+X, T" than I got message "No JUnit tests found". However when I try the same thing with mouse (right click and select "Run As \ Kotlin JUnit Test") then test is executed as expected.
Comment 1 Arnošt Havelka CLA 2019-11-29 02:58:37 EST
See my previously reported bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=553606. They might be related. However it's too different issues so I reported them separately.
Comment 2 Eclipse Genie CLA 2021-11-19 18:10:01 EST
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.
Comment 3 Eclipse Genie CLA 2023-11-10 04:47:58 EST
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.