Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 335665 - StepExecutionExceptions are not always handled by RC
Summary: StepExecutionExceptions are not always handled by RC
Status: CLOSED FIXED
Alias: None
Product: Jubula
Classification: Technology
Component: RC (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P2 critical (vote)
Target Milestone: Indigo RC1   Edit
Assignee: Zeb Ford-Reitz CLA
QA Contact: Oliver Goetz CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-28 04:56 EST by Markus Tiede CLA
Modified: 2011-06-14 09:36 EDT (History)
0 users

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 Markus Tiede CLA 2011-01-28 04:56:12 EST 
The StepExecutionExecptions which occurred in bug 335548 led to an UE in the AUT (in our case Jubula).
Comment 1 Zeb Ford-Reitz CLA 2011-01-28 10:52:20 EST 
From the stack trace, it looks like this would also occur in a pure SWT context. After a quick glance at o.e.jubula.rc.swing.swing.implclasses.SwingApplicationImplClass, it appears as though the error would occur in a Swing context as well.

When working on a fix for this bug, keep in mind that it seems to apply for multiple Toolkits, as well as multiple Actions. In short, do not just fix the problem for RCP + Wait for Window to Close.

Tests for the bug should also cover a wide range of Toolkits and Actions.
Comment 3 Oliver Goetz CLA 2011-06-14 09:36:34 EDT 
Verified for toolkits swing, SWT and RCP and actions "Wait for Window (+ matches)", "Wait for Window to close", "Wait for Window Activation" and several others like check, select etc. Since a complete check of all toolkits covering a wide range of actions seems too extensive this ticket gets closed after talking to AL.