Bug 541485 - [JUnit] Cannot navigate from JUnit view to source for JUnit 4 tests that have a parameter
Summary: [JUnit] Cannot navigate from JUnit view to source for JUnit 4 tests that have...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.10   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Roland Grunberg CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-23 02:32 EST by Noopur Gupta CLA
Modified: 2023-10-24 13:39 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Noopur Gupta CLA 2018-11-23 02:32:25 EST 
Follow up from bug 537286. See the discussion on its Gerrit patch also.

@RunWith(VertxUnitRunner.class)
public class JUnitTestSuite {
  @Test
  public void testSomething(TestContext context) {
    context.assertFalse(false);
  }
}

Run the test. Then, double-click on test method in JUnit view to navigate to the source. We get an error dialog.
Comment 1 Noopur Gupta CLA 2019-02-07 03:24:13 EST 
Roland, can you please investigate this?
Comment 2 Roland Grunberg CLA 2019-11-12 11:22:34 EST 
Not sure when I'll get the time to investigate, but I intend to look at this. Just unsure of timeframe.
Comment 3 Eclipse Genie CLA 2021-11-02 15:34:15 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 4 Eclipse Genie CLA 2023-10-24 13:39:49 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.