| Summary: | StepExecutionExceptions are not always handled by RC | ||
|---|---|---|---|
| Product: | [Technology] Jubula | Reporter: | Markus Tiede <markus.tiede> |
| Component: | RC | Assignee: | Zeb Ford-Reitz <zeb.ford-reitz> |
| Status: | CLOSED FIXED | QA Contact: | Oliver Goetz <Oliver.Goetz> |
| Severity: | critical | ||
| Priority: | P2 | ||
| Version: | unspecified | ||
| Target Milestone: | Indigo RC1 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Markus Tiede
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. 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. |