-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for XPath locator strategy #29
Comments
Second option needs more investigation. At least three ways to implement on the fly XPath-able collection are available:
Need to understand limitations and benefits of each one.
|
Implementing |
Successfully used for desktop, thanks for research |
Somebody packed System.Xml.XPath for Silverlight apps, see package here https://www.nuget.org/packages/System.Xml.XPath.SL4/ We should try it out |
Hi @NickAb . |
XPath or similar (
css selector
-like) locator strategy might be useful for apps that have complex UIs or not quite tuned for ease of testing.PageSourceCommand
and standardXmlDocument
, but it will requirePageSourceCommand
to be modified in a way that it will save all elements to registered elements storage. Such solution is easiest for implementation at the moment, but will be very slow as it will require whole UI visual tree to be traversed and represented as XML nodes regardless of actual XPath, which can match first node.XmlReader
, that would return nodes on the fly as needed, might be a better option in terms of performance. See Implementing XmlReader Classes for Non-XML Data Structures and Formats.The text was updated successfully, but these errors were encountered: