This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 162847 - jUnit navigation issue
Summary: jUnit navigation issue
Status: RESOLVED DUPLICATE of bug 171050
Alias: None
Product: java
Classification: Unclassified
Component: JUnit (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Andrey Yamkovoy
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-16 14:53 UTC by mjr_1974
Modified: 2009-10-28 22:37 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

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 mjr_1974 2009-04-16 14:53:31 UTC 
I think double clicking on the test name (the node in the JUnit window) should set the cursor exactly where the test is
defined, whether it failed or not.
Comment 1 mjr_1974 2009-04-16 14:59:33 UTC 
Currently if a test times out causing an error that needs to be corrected, there is no way to jump to it...
Comment 2 mjr_1974 2009-05-13 16:48:54 UTC 
Also, when JUnit fails a test, double clicking on the stack trace sometimes does nothing. This happens when the file I'd
like to go to is open in any of the windows of the editor as the active file. The expected behaviour is that double
clicking in the stack trace will take the cursor exactly to the line number showed in it.
Comment 3 mjr_1974 2009-08-11 20:22:55 UTC 
Sometimes clicking on the last stack trace line presented in JUnit Test window will redirect the cursor to the position
of the previous line of the stack trace. When that happens, clicking on the previous line redirects the cursor to the
expected line:

        at abc.config.AClassTest.finish(AClassTest.java:125)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:619)

double click on the first line will take you to FutureTask.java:303
double click the previous line will also take you to FutureTask.java:303

In the general output window the behavior is as espected:

double click on the first line will take you to AClassTest.java:125
double click the previous line will also take you to FutureTask.java:303
Comment 4 Victor Vasilyev 2009-10-28 22:37:11 UTC 
Seems all negative episodes described in this issue won't occur after the issue 171050 has been resolved. 
I'll mark this issue as duplicate.

*** This issue has been marked as a duplicate of 171050 ***