Skip to content
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

WinAppDriver vs UIAutomation library(UIAutomationClient.dll) #1994

Open
prash-19 opened this issue Apr 2, 2024 · 2 comments
Open

WinAppDriver vs UIAutomation library(UIAutomationClient.dll) #1994

prash-19 opened this issue Apr 2, 2024 · 2 comments

Comments

@prash-19
Copy link

prash-19 commented Apr 2, 2024

What are the benefits of WinAppDriver over UIAutomation library?
Does WinAppDriver use UIAutomation library internally?
What are the scenarios where I can use UIAutomation library over WinAppDriver?

@HowTurnRight
Copy link

Main benefit is that you can use selenium webdriver syntax and you don't need to learn any new libraries.

@PandaMagnus
Copy link

As far as I understand, yes WinAppDriver (at least partially) uses UIAutomation library under the covers. It's the primary hook into interacting with desktop applications outside of invoking some Windows APIs directly. I've used UIA directly, and I have a coworker that has done the latter. Neither is trivial (although UIA was considerably easier to manage,) so one benefit to tools like WAD and FLAUi is that they're easier to deal with as an abstraction on top of those lower level calls.

You technically could likely use UIA totally in place of WAD. I've thought about doing that since WAD is no longer maintained.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants