Community
Participate
Working Groups
Build Identifier: STandalone version 0.9.0.qualifier Hi, When running a recorded test case, I always get an error 7009 with the 'Wait for Window' and 'Wait for window to close'. I can easily workaround it, setting the 'Delay after Visibility' to 1000 instead of the default 500. I now use a variable (instead of setting it hard to 1000) which I set in a central data set that I link to all my test cases. I don't think this is a bug (i am even pretty sure :-), but rather application (and OS/Hardware) dependent. But wouldn't it be an overall enhancement for the project you would be able to define (ex. in the preferences point to a central data set) the default values of the parameters of the components the observation mode should use when inserting test steps? Regards, Marc J. Reproducible: Always Steps to Reproduce: 1. just run observation mode 2. 3.
Wouldn't it be even better to register the real time between manual actions and insert that delay as a wait between each test step registered during observation mode. This way the replay will be an exact copy of what is done by the user. If the replay does not work then, this means something is different about the test and this means it needs investigation and thus should trigger an error. regards, Marc
I am changing this enhancement to a bug, as the Test Execution Error is a result of a component name (probably the default application name) not being resolvable. After making a change (any change) to the Test Case and re-running the test, the error no longer occurred, so the problem appears to have a simple workaround. Nevertheless, it is an error. 7009: Test Execution Error. The component name "a31d947efd664b46a8d02b36acbb96b2" in Test Case "Observed1" in Test Step "Wait for Window to Close" can not be resolved. Please make sure that all of your reused Projects are currently available in the database and not marked as missing in the Test Case Browser.
I'm going to set this to wontfix for the following reasons: - The observation mode isn't the preferred / suggested way of working. It's only really supposed to help with absolute beginners to see how Jubula thinks. - There is a simple workaround. If this becomes more pressing or is rediscovered with a new severity, then the bug can be reopened.
Closed due to comment 3.
