|Re: Event handler does not propagate component name: Workaround wanted [message #1405365 is a reply to message #1405099]
||Thu, 07 August 2014 07:35
| Florian Lenzner
Registered: July 2014
Yes, in the above case, component name A was propagated, but not component name B. (I need to click on B to bring up A, basically).|
I found one possible workaround, which is a bit ugly, though:
TC "Provide dialog"
- Check for non-existence [component name A]
- <open dialog>
- Event handler: <NOP>
The NOP test case does nothing. The event handler has reentry type of RETURN. In case component A is there, the check fails, and the event handler returns from the test case. This works, but makes the test fail in case the dialog (component A) is already there - not very nice. Actually, this is not what you want in your tests, so eventually, I'm using separate modules.
Powered by FUDForum
. Page generated in 0.21274 seconds