#114 Test Stack Trace Non-Obvious
As of 20020913-2254, the test results pane does not show the stack traces for failures. The only way to access these traces is to pull up the contextual menu for the item by clicking on it within the text pane. There should be some other indication that this information is available, since context menus on text panes generally provide only edit controls. It is also bad form to have features hidden through access methods that are not visually discoverable.
A secondary issue is the display of the stack trace in a modal dialog window. It is unnecessarily difficult to troubleshoot the source of a test failure, since it is impossible to work in DrJava while the stack trace dialog is being displayed. This information should be available in a less obtrusive manner, IMHO.
Logged In: YES
user_id=429731
I agree that there needs to be some other indication.
Putting a button next to each failure seemed a little
clumsy, but might be the best way to go. I'm a little
hesitant to put a button in the right part of the panel,
since I'm just finishing up putting a progress bar there.
I'll experiment and see what looks best.
As for the modal dialog, I was opposed to it at first, but
Theo insisted that having it be non-modal allows the dialog
to become out of date. (A user can open a stack trace
window, go back to DrJava, then click on a different error.)
Changing the trace in the window is a little strange, and
opening multiple trace windows would be cluttered. If you
can recommend appropriate behavior for a non-modal dialog,
I'm open to it.
Logged In: YES
user_id=1075744
Originator: NO
Re-classified as feature request.
I didn't even know about the context menu, and I've always overlooked the "Show Stack Trace" button, so I think something should be done about this.
1) How about a "verbose" view that includes the complete stack trace for each failure?
2) Or what about splitting the pane into a left and a right half, and displaying the stack trace in the right side?