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.
In NetBeans 6.7 the Maven support switched to the common test runner. When I right click on failed tests or on their stack dump there is a Go To Source menu item. When I click it, nothing happens. This is a badly needed feature, please fix it before release.
The actions for the nodes are configured on the Maven side. Not a JUnit issue. Reassign to maven for evaluation.
same comment as in 166144, with the sample project I'm able to use the feature both with build invoked by maven and by ant (via Compile On Save). reassigning to dsimonek for deeper evaluation, could be platform dependent, in any case we would need some sample project and detailed steps to reproduce.
In the JUnit test results window I right click the test class that had a failure, select go to source, and it opens the test class with the cursor at the very top. Next I try right clicking the failed test and clicking go to source expecting it to take me to the method in the test class that failed. When I click Go To Source my computer beeps at me and nothing happens. My projects cannot be shared since they are closed source and private for a customer. Sorry
I tried this on a tiny project with just one test class and one test in it. When I right click the failed test and select Go To Source, it opens the test class and puts the cursor at the method that failed. This is what I expect. The project where this doesn't work has many test classes and hundreds of tests.
Works for me OK on sample project that I assigned to 166144. Please try to provide some sample project on which this issue is reproducible, otherwise I will not be able to do anything but close this report, thanks.
Without requested information for long time - WORKSFORME. We can't do anything in this case. Reporter, please add requested information and reopen issue. Thanks in advance.