Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 343580 - provide actions on test results in build editor
Summary: provide actions on test results in build editor
Status: CLOSED MOVED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-21 12:19 EDT by Eugene Kuleshov CLA
Modified: 2011-05-16 11:36 EDT (History)
1 user (show)

See Also:

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 Eugene Kuleshov CLA 2011-04-21 12:19:19 EDT 
Currently doubleclicking the test results in build editor opens a source code in Eclipse workspace (if available), however for tests it is more common to see the actual error and the stack trace. But the only way to see the stack trace from build editor is to clivk on "open in junit" view, which is by the way a bit out of context (should be really on a toolbar for the test results).

I'd suggest to change the double click to open test results in default Java Stack Trace console and also add a popup menu (trough standard object contribution) for several additional actions. For example: open test source, open test in JUnit view, run, debug, etc
Comment 1 Steffen Pingel CLA 2011-05-16 11:36:26 EDT 
Sounds like a very good suggestion.
Comment 2 Eclipse Webmaster CLA 2022-11-15 11:45:08 EST 
Mylyn has been restructured, and our issue tracking has moved to GitHub [1].

We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub.

[1] https://github.com/orgs/eclipse-mylyn