Bug 535252 - [JUnit 5] Menu "Search > Referring tests" does not work with JUnit5
Summary: [JUnit 5] Menu "Search > Referring tests" does not work with JUnit5
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.8   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2018-05-29 00:57 EDT by Dieter Scholz CLA
Modified: 2022-06-09 11:02 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dieter Scholz CLA 2018-05-29 00:57:52 EDT
Hello,

when I execute the menu item "Search > Referring tests" a dialog appears that Junit4 needs to be on the classpath. But I would like to use this function with JUnit5. Any plans to fix this functionality?

Regards, Dieter
Comment 1 Noopur Gupta CLA 2018-05-30 01:41:01 EDT
Please attach a sample project containing both JUnit 4 and JUnit 5 tests which are referring to a type/method/file from that project, such that the "Search > Referring tests..." option is working for JUnit 4 and not for JUnit 5. This will help to reproduce the issue.

Also, provide more details on what is your current selection while invoking this option.
Comment 2 Eclipse Genie CLA 2020-05-25 02:23:47 EDT
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 2022-06-09 11:02:37 EDT
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.