List Icon
Mailing list Archive

2019 up to July 2022 | 20182017  |  2016  2015 2014 | 2013

The mailing list has been closed since July 2022, but continues to serve as an archive of information about QF-Test.
If you want to stay informed about news about QF-Test, you can simply subscribe to our newsletter:
Subscribe to Newsletter  


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

  • Subject: [QF-Test] Interworking between 'waitForComponent', rc.getComponent and rc.getOverrideElement
  • From: Bernhard Schmitt <bernhard.schmitt@?.de>
  • Date: Mon, 20 Feb 2017 14:15:23 +0000
  • Delivered-to: qftest-list@?.net



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?









Bernhard Schmitt

Consultant Softwaretest

E-Mail: bernhard.schmitt@?.de


imbus Rhein-Main GmbH, Kirschgartenstraße 15, 65719 Hofheim, DEUTSCHLAND

Tel. +49 6192 92192-0, Fax +49 6192 92192-50



Geschäftsführer: Frank Schmeißner, Tilo Linz, Thomas Roßner

Sitz der Gesellschaft: Hofheim

Registergericht: Frankfurt am Main, HRB 52155