When trying to identify objects in browsers, I often experience limitations (or differences) in Ranorex Spy compared to direct search in for example Chrome. Example:
//div[contains(@class,'some text')]//span[.='Some text']
Works fine in Chrome, but not in Ranorex Spy. Seems like "contains" is not supported. Many other examples like this.
Are the limitations or differences in Ranorex documend somewhere? Any other genereal guidelines / rule of thump?
Best Regards
Bo
Documented lImitations in Ranorex use of xpath?
Documented lImitations in Ranorex use of xpath?
Best Regards
Bo
Bo
Re: Documented lImitations in Ranorex use of xpath?
Hi,
I'm afraid, Ranorex xpath implementation does not offer all functions and operators available in general xpath definition. You will have to live with operators and functions described in Ranorex User guide.
BTW, there are few missing xpath functions in Ranorex user guide:
I'm afraid, Ranorex xpath implementation does not offer all functions and operators available in general xpath definition. You will have to live with operators and functions described in Ranorex User guide.
BTW, there are few missing xpath functions in Ranorex user guide:
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
Re: Documented lImitations in Ranorex use of xpath?
OK. Thanks much for your quick reply. Very valuable. Now, at least, I know what the limitations are. I'll probably have to put some extra pressure on development on naming their stuff 
Great list of additional functions.
Ranorex team, if you are "listening in", it would be great to have a complete list of supported operators/functions in the documentation.

Great list of additional functions.
Ranorex team, if you are "listening in", it would be great to have a complete list of supported operators/functions in the documentation.
Best Regards
Bo
Bo