-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Finding elements according to inspect.exe #2034
Comments
@Shakevg Could you give me a demonstration of how to implement the PageSource, I am getting a HTTP/1.1 500 Internal Error from the Windows Driver console when I try it. |
@Kevv55 I get a 500 error also. I just write it to a text file to evaluate. |
@liljohnak how can I do this? Could you show me an implementation?? WinAppDriver works perfectly with Notepad & Text-file automations, but with the win32 application I am trying to automate it fails to find a lot of the UI elements |
I can find the element names, on both inspect.exe and Accessibility Insights but when I use FindElementByName() function it returns the following error:
My assumption is because I want to click on an element that is a combo box and is the child of other elements (element tree screenshot from Accessibility Insights below). When I try to use the FindElementByName() on the parent elements I get the same error, FindElementByClass does not produce anything for the UI elements that inspect.exe/Accessibility Insight display the class name, and I wouldn't know how to find the Xpath of the UI element.
Element I am trying to access:

My first question is: In a WindowsDriver session is there a way to display the names of the available elements, so finding them by trial and error can be reduced.
Below is my code, it is written to Automate a Win32 application, everything works until the point where I have to find the "cbocode" combo box element:
}
I was having problems with the splashscreen so I debugged it all to ensure the WindowHandle only changes after the splashscreen.
My main problem is having something clearly described by inspect.exe/Accessibility insight but not being able to find it via FindElementbyName/ID/Class. Why is the Windows driver able to find some elements but not others, and how can I go around this to be able to click and move into those elements?
I know there are probably more effective ways to write this code, so if you could also leave a link where I could find all the documentation needed with the functions available for OpenQA.Selenium.Appium.Windows api I would really appreciate it.
The text was updated successfully, but these errors were encountered: