dom vs form object identification : General Questions

[rkarhe]

Hello,

While tracking UI elements, SPY gives form and dom based object identification. Earlier I used to work with form based identification but I found it as very slow. Just to optimize the speed I have tried same UI element through dom and found it has great performance. Just want to confirm whether my findings are correct? Is there any specific reason SPY gives both form and dom based identification?

Thanks,
Rocky

[Support Team]

Hi,

While tracking UI elements, SPY gives form and dom based object identification. Earlier I used to work with form based identification but I found it as very slow. Just to optimize the speed I have tried same UI element through dom and found it has great performance. Just want to confirm whether my findings are correct? Is there any specific reason SPY gives both form and dom based identification?

Sorry but currently I have no plan what do you mean. Please could you explain your issue in more detail?

• Which technology do you use?
• Are you testing a web or other kind of application?
• and so on...

Regards,
Peter
Ranorex Team

[rkarhe]

Well, I will try to re-explain my findings with example.
Let's say I have a ui element having innertext as "Ranorex", this element is on page having title "Welcome to Renorex" and inside table having id as "ranorexId".
When I will track this through Ranorex Spy, ranorex will say me that 2 elements found and RxPath will be something as follows
1)/form[@title="Welcome\ to\ Renorex"]//table[@id="ranorexId"]//span[@innertext="Ranorex"].
2)/dom[@domain="DOMAIN_NAME" @caption="Welcome\ to\ Renorex"]//table[@id="ranorexId"]//span[@innertext="Ranorex"].

Spy identified the element as /form object and as /dom object. So I have following queries.

- Why is that SPY gives 2 way identification of elements. Is there any specific reason behind this?
- I observed /dom way identification of elements is faster than /form way identification. What is your take on this?

Find my comments on your questions.
Which technology do you use?
- c# with ranorex 3.0.4

Are you testing a web or other kind of application?
- web application.

and so on...

I hope I have explained the issue, Let me know if required more info.

Thanks,
Rocky

[Support Team]

Hi,

this is a feature provided by Ranorex to shorten the way to get to your DOM object.
All DOM objects in you GUI hierarchy will be shown as direct descendants of the root node as well as the normal representation nested in the form object it's regarding to.

By doing so you do not have to pass through the whole path to get to the specific elements which will speed up identification.

So it's recommended to use the extracted DOM object instead of using the form object with the nested DOM object.

Kind regards,
Tobias
Support Team