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

Bug 343344

Summary: Following access to same menu item fails in RCP
Product: [Technology] Jubula Reporter: Felix Ziesel <Felix.Ziesel>
Component: UIAssignee: Project Inbox <jubula.ui-inbox>
Status: CLOSED INVALID QA Contact: Oliver Goetz <Oliver.Goetz>
Severity: critical    
Priority: P3    
Version: 0.9.0   
Target Milestone: 1.0   
Hardware: PC   
OS: Windows Server 2008   
Whiteboard:
Attachments:
Description Flags
Screenshot of the test result after failing
none
Lib to reproduce none

Description Felix Ziesel CLA 2011-04-20 03:13:39 EDT
Created attachment 193657 [details]
Screenshot of the test result after failing

The following test fails:

1. check a menu entry for existence (Window-> Show View -> VIEW NAME)
2. check a menu entry for enablement(Window-> Show View -> VIEW NAME)

The test fails with error message 'The submenu for "Window" did not appear.' at test case 2. If I change the order of the test cases, the error occured again at the last test case. The error also occured when I use another View name for the second test case. It does not appear if I use another Top menu ("Run" instead of windows).
Waiting for one second between the two test cases shows the same error.

The error occured on Eclipse Helios SR 2 and Eclipse Indigo M6a 32 bit.
Comment 1 Felix Ziesel CLA 2011-04-20 03:27:05 EDT
The last comment contains an error.
The error occured only on Eclipse Indigo M6a 32 bit.
Eclipse Helios SR 2 works fine.
Comment 2 Felix Ziesel CLA 2011-05-16 03:08:52 EDT
Created attachment 195693 [details]
Lib to reproduce

The added library can reproduce the error if you use the module ub_syn_mbr_assertAvailability(TEXTPATH,OPERATOR).

You have to open it, remove the workarounds (the TODO and POST test step) and use it in your RCP test suite.
The error occurs rarely when using the workaround too.
Comment 3 Felix Ziesel CLA 2011-05-18 03:09:54 EDT
This error can be masked by using a synchronized method with retries for an wait.
Therefore I will close it. The polling needs some time so you should set the timeout to nothingh less than 50 millisecsonds.