Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 318793

Summary:	[KeyBindings] Right after starting up eclipse, the keyboard shortcut to run a junit test never works
Product:	[Eclipse Project] Platform	Reporter:	Peter De Maeyer <peter>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	mr.gruust
Version:	3.5.2
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:	stalebug

Description Peter De Maeyer

2010-07-03 13:38:25 EDT

Build Identifier: M20100211-1343

Ubuntu 10.04, Linux-GTK x86_64.

I usually use the key combination to run a junit test SHIFT+ALT+X T. However, this keyboard shortcut never works _immediately_ after eclipse starts up. It only works _after_ I've run a junit test via the mouse menu once.

Reproducible: Always

Steps to Reproduce:
1. Start up eclipse on a java project, open a junit test and run it
2. Restart eclipse, the junit test you have open in the previous step should still be open
3. Try running the unit test using the keyboard shortcut SHIFT-ALT-X T. Nothing happens, it seems the keyboard shortcut doesn't work.
4. Run the junit test using the context menu richt-click->Run as->JUnit test, and the test will run.
5. Try the keyboard shortcut again: the junit test runs. From now on, the keyboard shortcut works, but it never does the first time around.

Comment 1 Prakash Rangaraj

2010-07-29 05:02:11 EDT

Paul,

    Should we move this to platform-debug to investigate?

Comment 2 Paul Webster

2010-07-29 07:47:02 EDT

This is a known bug, a side effect of the Eclipse platform lazy loading strategy.  When I find the open bug we can mark it as a dup.

PW

Comment 3 Mr Gruust

2017-06-16 07:47:42 EDT

Seven years later, one of the most prominent and visible bugs is still unfixed. Anyone alive?

Comment 4 Mr Gruust

2017-06-16 07:49:25 EDT

Maybe this is a sign that Eclipse should follow the path of NetBeans and move to the Apache Foundation, maybe to merge both IDEs there?

Comment 5 Mr Gruust

2017-06-21 15:23:26 EDT

btw: if I re-run the last unit test right after start-up, using the short-cut for executing the last command/build, *that* works. Appearantly, that short-cut has no issue with lazy-loading. ?

Comment 6 Eclipse Genie

2020-02-11 12:20:31 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.