Searching for a web element takes ~ 25 seconds
Posted: Sun Jun 19, 2011 9:02 pm
Hi all,
We are using Ranorex to automate various activities across all product suites in the company.
While working on some web component, i've encountered an issue with identifying an element on the page.
The XPath to the element is something similar to:
body/div/div[@id='SuiteNavigation']/div/div[@id='systemApplications']/table/tbody/tr/td[14]
On another scenario the same element has this path:
body/div[@id='SuiteNavigation']/div/div[@id='systemApplications']/table/tbody/tr/td[14]
In order to keep my code consistent, i've looked for a proper generic way to have both options valid under a single repository item, which led me to have this:
body//div[@id='SuiteNavigation']/div/div[@id='systemApplications']/table/tbody/tr/td[14]
The original item identification takes ~ 1 second
With // (match any descendant) it takes ~ 25 seconds.
Is there a way to improve on this, as this is unacceptable performance from our side?
Thanks
Lior
We are using Ranorex to automate various activities across all product suites in the company.
While working on some web component, i've encountered an issue with identifying an element on the page.
The XPath to the element is something similar to:
body/div/div[@id='SuiteNavigation']/div/div[@id='systemApplications']/table/tbody/tr/td[14]
On another scenario the same element has this path:
body/div[@id='SuiteNavigation']/div/div[@id='systemApplications']/table/tbody/tr/td[14]
In order to keep my code consistent, i've looked for a proper generic way to have both options valid under a single repository item, which led me to have this:
body//div[@id='SuiteNavigation']/div/div[@id='systemApplications']/table/tbody/tr/td[14]
The original item identification takes ~ 1 second
With // (match any descendant) it takes ~ 25 seconds.
Is there a way to improve on this, as this is unacceptable performance from our side?
Thanks
Lior