Hello again Ranorex Support,
our customer has a web based application with a circle (see screenshot). The circle has several elements that need to be validated in the run time, like changing colors or clicking on one of the grey parts to open detailed information. Changing the circle elements or the circle rotation speed happens via web services.
As long as the circle stands still, getting properties of any of those items is working fast. But as soon as the circle starts to move (it needs ~15 minutes for one complete round), Ranorex takes a long time (> 10 seconds per action or even more) to read out properties or perform any action on the object. Our testcase took more than 15 minutes to run, which could be done in under 2 minutes.
Is there any best practice to work with moving objects or does Ranorex have any possibilities I could use to work with that accelerate the testing process?
Working with CaptureBitmap is not an option because I also need to check html properties of the grey boxes.
Example of the circle:
I nearly forgot:
Ranorex Version 5.3.3 on Windows Server 2012 R2
Best regards,
Rafael
Slow object identification on moving web objects
Slow object identification on moving web objects
You do not have the required permissions to view the files attached to this post.
- Support Team
- Site Admin
- Posts: 12145
- Joined: Fri Jul 07, 2006 4:30 pm
- Location: Houston, Texas, USA
- Contact:
Re: Slow object identification on moving web objects
Hello Rafael,
Depending on how the circle is rendered and animated, the element tree might be changing, which would make the RXpaths only work when the circle is on a specific location.
Can you please provide a snapshot file of the element in question? That should allow us to find the cause of the issue.
Thanks,
Hansel
Depending on how the circle is rendered and animated, the element tree might be changing, which would make the RXpaths only work when the circle is on a specific location.
Can you please provide a snapshot file of the element in question? That should allow us to find the cause of the issue.
Thanks,
Hansel
Re: Slow object identification on moving web objects
A snap shot for the moving object is attached!.
You do not have the required permissions to view the files attached to this post.
Re: Slow object identification on moving web objects
A snapshot for the moving object is attached.
Re: Slow object identification on moving web objects
Hi Hansel,
sorry for the delay in replying. Here is a snapshot of the object.
Best regards,
Rafael
sorry for the delay in replying. Here is a snapshot of the object.
Best regards,
Rafael
You do not have the required permissions to view the files attached to this post.
Re: Slow object identification on moving web objects
Hi,
At first, have you tried your test scripts with latest 5.4.1 (even in trial mode)? Just to check if there is any speed difference.
Next, could you please post an example path you are using to identify the individual elements?
The good thing is that the numbered sectors contain InnerText with the actual number of each sector (from 1-32). It's probably better way to identify the numbered sectors by these numbers instead of the non-descriptive "embernnnn" unique IDs. On the other hand, using unique IDs could speed up the element search.
Are these unique IDs persistent? I mean, could you please verify if let's say section "32" is always inside div "ember1187"? Here is an example path you can use to identify section "32" using its innertext...
And this is the path you can use to identify the large "grey" section above section 32...
/dom[@domain='10.150.1.246:8080']//div[@id~'ember']/div[@innertext='32']/../div[@class='box']/div[@class='ember-view box-inner']
At first, have you tried your test scripts with latest 5.4.1 (even in trial mode)? Just to check if there is any speed difference.
Next, could you please post an example path you are using to identify the individual elements?
The good thing is that the numbered sectors contain InnerText with the actual number of each sector (from 1-32). It's probably better way to identify the numbered sectors by these numbers instead of the non-descriptive "embernnnn" unique IDs. On the other hand, using unique IDs could speed up the element search.
Are these unique IDs persistent? I mean, could you please verify if let's say section "32" is always inside div "ember1187"? Here is an example path you can use to identify section "32" using its innertext...
Code: Select all
/dom[@domain='10.150.1.246:8080']//div[@id~'ember']/div[@innertext='32']
/dom[@domain='10.150.1.246:8080']//div[@id~'ember']/div[@innertext='32']/../div[@class='box']/div[@class='ember-view box-inner']
You do not have the required permissions to view the files attached to this post.
Pavel Kudrys
Ranorex explorer at Descartes Systems
Please add these details to your questions:
Ranorex explorer at Descartes Systems
Please add these details to your questions:
- Ranorex Snapshot. Learn how to create one >here<
- Ranorex xPath of problematic element(s)
- Ranorex version
- OS version
- HW configuration