Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 335548 - Configuration Error on "Wait for Window to Close" Action
Summary: Configuration Error on "Wait for Window to Close" Action
Status: CLOSED FIXED
Alias: None
Product: Jubula
Classification: Technology
Component: RC (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 blocker (vote)
Target Milestone: ---   Edit
Assignee: Markus Tiede CLA
QA Contact: Oussama CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-27 04:40 EST by Alexandra Schladebeck CLA
Modified: 2011-02-04 08:24 EST (History)
1 user (show)

See Also:


Attachments
Malformed regular expression (7.57 KB, text/plain)
2011-01-28 04:03 EST, Markus Tiede CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandra Schladebeck CLA 2011-01-27 04:40:09 EST
The action "Wait for Window to Close" in the nightly regression test for RCP applications failed immediately with a "Configuration Error". The action "Wait for Window" was successful.
Comment 1 Markus Tiede CLA 2011-01-27 06:10:52 EST
I am currently not able to reproduce this error - it may be somehow related to recent logging problems. Unfortunately the same logging issue (see bug 334999) complicates the analysis of this nightly related issue, as there are currently also no nightly log-files available. I recommend attaching the log-files as soon as they are available again if this issue is still present.
Comment 2 Markus Tiede CLA 2011-01-28 04:03:01 EST
This error re-occurred during the nightly regression tests and this time the logs are available (and attached).

The problem is that the given "title"-regular expression is malformed: It's specified as "*.Progress.*" instead of ".*Progress.*". Furthermore the error message should be more detailed.
Comment 3 Markus Tiede CLA 2011-01-28 04:03:27 EST
Created attachment 187812 [details]
Malformed regular expression
Comment 4 Markus Tiede CLA 2011-01-28 04:25:35 EST
It seems as if the error message itself is already correctly being wrapped in a StepExecutionException and an "action error - malformed reg exp" as the test error event. It seems as if this StepExecutionException is not handled correctly in the context of an RCP-based application, as it e.g. leads to an UE in the AUT (in our case Jubula) instead of being used to communication the problem back to the test execution controller (in our case the commandline client / test result).

I will open a new bug for this issue - the QA should resolve the malformed pattern.
Comment 5 Alexandra Schladebeck CLA 2011-01-28 05:25:33 EST
Malformed pattern has been resolved in the test.
Comment 6 Oussama CLA 2011-02-04 08:24:50 EST
Malformed regular expression has been resolved from the test.