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.
I'm looking at the 6.8 beta Junit window and noticed something new. No matter how *wide* my junit window is, apparently there is some limit to how many chars a method length may have. So, instead of the normal text in the tree node that looks like com.package.ClasSName(line) I get something like com.package.Class...(13 chars omitted). Well, this is buggy on multiple levels: * resizing the view should refresh the nodes text display and show me the actual text ! I especially need the line number for example. * "...(13 chars omitted)" is 21 chars long. I don't see the economy realized by not showing me 13 chars and adding 21 instead... * the navigation seems to be broken. If I go into the Consolo and I click on the junit test lines, the editor jumps properly. In test test I'm looking at, I have to overloaded methods in the unit tests where one just calls the other. Clicking on the nodes in the tree jumps the editor to the same "base" method.
emi, thank you for bringing up this issue. > No matter how *wide* my junit window is, apparently there is some limit to how many chars a method length may have. A cause for such "strange" behavior of the JUnit test result window is the Issue 172772 . Now, lengths of all messages are limited up to 80 characters. > the navigation seems to be broken. A cause of this is a bug reported in the Issue 171050. It is fixed in build *200910221401* Please, use the following workaround for now: - download and use a latest build ( http://bits.netbeans.org/dev/nightly/ ) to have correct navigation from the JUnit test result window to the source code. - set a desired and appropriated length limit for the messages displayed in the JUnit test result window. Default message length can be changed via a system property, e.g. use the option "-J-Dtestrunner.max.msg.line.length=150" for the netbeans command to set the message length to 150. How I plan to fix this issue? 1. Increasing of a limit of the messages length up to 320 characters. 2. Avoiding of cutting off a message tail if a notification message (e.g. "...(13 chars omitted)") is longer. I hope, after my clarification you'll agree that this issue can be considered as P3.
Fixed in the main trunk http://hg.netbeans.org/main/rev/81b30d6cc217
Thanks for the quick reply. Indeed, your fix seems to resolve this report partially. I haven't actually tested that new build so I'll just wait for the navigation be be live in the next beta. I'll comment some more about the JUnit solution in the other bug reports.
For the "n chars omitted" see bug 268472.