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 84522 - JUnit Test Results page - go to source
Summary: JUnit Test Results page - go to source
Status: RESOLVED DUPLICATE of bug 71356
Alias: None
Product: java
Classification: Unclassified
Component: JUnit (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker with 1 vote (vote)
Assignee: junit-issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-08 16:13 UTC by wqtnetbeans
Modified: 2009-03-27 11:54 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description wqtnetbeans 2006-09-08 16:13:37 UTC
In the JUnit Test Results page, there should be a "go to source" function when
the user double click (or right click -> go to source) the fully qualified class
name. The user should be able to navigate to the source on any class that is
within the opened project.

Currently the only way to go to source code is when some error happens in a test
case, and the user double click the class name (Even this sometimes does not
work!).
Comment 1 mjr_1974 2008-05-21 20:08:35 UTC
I have this very same issue in Netbeans 6.1 too
Comment 2 dschulten 2008-12-21 22:06:53 UTC
It seems the situation has deteriorated.
In 6.5 it is not possible to go from a failed test in the Junit Test Result Window to the corresponding source at all.

Steps to reproduce:
- Create Quickstart Archetype Project
- Create Class with one method
- Use Tools-Create JUnit Tests to create a test

The failure is reported with the correct line number, but the test result tree does not allow to navigate to the source.

Probably this is a well known problem which is not easily solvable. In that case, can you give a hint what the
underlying problem is?
Comment 3 cms 2008-12-23 10:35:37 UTC
Yes, this is a known problem. The Go To Source feature now works for selected project types only and so far Maven based 
projects are not in the scopes of this selection. 

The issue will be fixed later (it is planned to propagate common Go To Source SPI which should be implemented by all 
project types interested in Unit testing.)

Comment 4 Alexei Mokeev 2009-03-27 11:54:45 UTC

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