Re: [QF-Test] Interworking between 'waitForComponent', rc.getComponent and rc.getOverrideElement

[Gregor Schmid <Gregor.Schmid@?.de>]

Hello Bernhard,

that's a very good question.

The problem is that rc.getComponent has a 0 timeout because it blocks
the event dispatch thread. This means that you have to run
'WaitForComponent' first so that you can be sure to pick up the
correct component in rc.getComponent. Unfortunately rc.getComponent
then incurs the same overhead again.

We'll see about introducing a doctag to the WaitForComponent node that
puts the resulting component directly into rc.overrideElement. That
should be preferable to using a WaitForComponent plus a script node
even when the overhead is minimal. 

Best regards,
    Greg

Bernhard Schmitt <bernhard.schmitt@?.de> writes:

> Hello,
>
> I have a short technical question. Consider a web application with a component which is not easy to recognize and
> which takes a while until QF-Test has mapped it to its internal component.
>
> Our purpose is, to cache such a component with rc.overrideElement(), so that the time expensive recognition happens
> only one time.
>
> So the question is, what happens inbetween  'WaitForComponent' and rc.getElement, and rc.getOverrideElement().
>
> 1.       When WaitForComponent(id) succeeds, is it certain that the web component is accesible and I can immediatly
> cache it with rc.getOverrideElement(id)
>
> 2.       When I call rc.getComponent(„id“) after WaitForComponent(id) succeeds, ist the component recognized again
> with the same time effort as before?
>
> BR
>
> Bernhard

-- 
Gregor Schmid

E: gregor.schmid@?.de
T: +49 8171 38648-11
F: +49 8171 38648-16

Quality First Software GmbH | www.qfs.de
Tulpenstr. 41 | 82538 Geretsried | Germany
GF Gregor Schmid, Dr. Martina Schmid, Karlheinz Kellerer
HRB München 140833