Hi Abhay,
I have been facing performance issues with different find methods especially in chrome. To filter out try putting a timer or a log message and confirm if page.FindChildByXPath is the line that is taking time.
iTime = Timer() Set obj = page.FindChildByXpath Log.Message "Time taken to find the object: " & Timer()-iTime & " secs"
If Yes, try finding the object by CSS Selectors or Find Method.
Regards
Osaid
Champion Level 2Hi Abhay,
In addition to what was said by Osaid: .FindChildByXPath is the last resort way in TestComplete's world and personally I can recommend to use it only when the web elements on the tested web page have no other identifiers but class name. In all other cases, search using .FindXXX methods provided by TestComplete is more preferable.
There are at least two reasons in favor of .FindXXX:
a) .Find is faster than XPath (confirmed by direct measurements);
b) in some cases, XPath search may return native web element but not TestComplete object (see documentation for more details) and thus you may not be able to use regular methods/properties like .Exists, .Visible, etc. for these native web objects and will have to determine first whether native web or TestComplete's object was returned as a result of XPath search.
