-
Notifications
You must be signed in to change notification settings - Fork 187
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
Feature/win #158
Feature/win #158
Conversation
@yodurr Can you add the AccessibilityID test to this branch please? |
what about code like this in WindowsMultiSelectControlTest.cs? What other Accessibility ID API do you want to test? Also I still don't follow why we need the IFindByWindowsUIAutomation namespace if the default API for finding by Accessibility ID works. |
@yodurr IFindByWindowsUIAutomation allows for much more complex queries than just locating an element by it's AccessibilityID. It could also allow for complex interactions. For example, here is an Android query that would scroll a scrollable view so that a view with a description containing
@TikhomirovSergey Do you have any thoughts on this and are you happy with @yodurr's proposed AccessibilityId example test? |
{ | ||
//return CollectionConverterUnility.ConvertToExtendedWebElementCollection<W>( | ||
// this.FindElements("-windows uiautomation", selector)); | ||
throw new NotImplementedException(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
May be there is sence remove this string and make this string not commented
return CollectionConverterUnility.ConvertToExtendedWebElementCollection<W>(
this.FindElements("-windows uiautomation", selector));
It depends on server-side and when it would be available then it should work immediately
It looks ok. I want to publish one more (not major) build and then merge this PR. I would like to ask you for a sample of the windows automation searching (you can post it as a comment). PS: I would like to add similar changes to the Java client with @JonStoneman authorship. Is it ok? |
/// Finds a list of elements that match the Windows UIAutomation selector supplied | ||
/// </summary> | ||
/// <param name="selector">a Windows UIAutomation selector</param> | ||
/// <returns>IWebElement object so that you can interact that object</returns> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please correct summary
@JonStoneman |
@JonStoneman This PR was mergen successfully. Now you are free to develop it further. Also I'm going to improve some thing. Thank you for the contribution. I hope we will cooperate further. :) |
Great! - thanks @TikhomirovSergey :) |
Change list
Add
WindowsDriver
andWindowsElement
for use with https://github.com/appium/appium-windows-driverTypes of changes
What types of changes are you proposing/introducing to .NET client?
Put an
x
in the boxes that applyDetails
Some methods throw NotImplementedExceptions due to https://github.com/Microsoft/WinAppDriver/ (and therefore https://github.com/appium/appium-windows-driver) not supporting the functionality.