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

[Feature] Run appium-windows-driver on Linux/macOS and connect to WinAppDriver on remote machine #281

Open
nicerloop opened this issue Oct 23, 2024 · 5 comments

Comments

@nicerloop
Copy link

Hi,

I would like to run appium-windows-driver on Linux/macOS and connect to a remote WinAppDriver.

Is this feasible with appium-windows-driver as is today?
Can I have some directions to try and implement this feature?

Thank for the good work.

@bmarroquin
Copy link

You would need to run appium + appium-windows-driver on the windows machine and connect it from an appium-client lib.

@nicerloop
Copy link
Author

That is what I do today, but I would like to lighten to the maximum the installed components on the Windows VM I use.

How is the connection between appium-windows-driver and WinAppDriver setup ?
What would need to be changed to allow connecting to a remote WinAppDriver ?
Which features are handled locally by appium-windows-driver, and would thus be lost when running outside the target machine ?

@bmarroquin
Copy link

The appium-windows-driver starts a WinAppDriver process on the same host it is running and then provides a proxy to that process. The proxy is hard coded to forward requests to 127.0.0.1. You would need to set up configuration options to skip starting WinAppDriver locally and then an option to change the proxy server IP. You would probably be required to something with the port as well.

You will then run into some problems. The WinAppDriver only implements a subset features available within appium-windows-driver. Everything in the commands directory would not work. You would need to figure out how to forward that to the remote as well.

Implementing that just to reduce the size of a VM doesn't seem worth it to me.

@nicerloop
Copy link
Author

Well, the problem is not mainly with the raw size, but the fact that nodes has some difficulties to run in some virtualized environments (VirtualBox). See the numerous duplicates of libuv/libuv#1633 still popping for 7 years, like libuv/libuv#4249.

@nicerloop
Copy link
Author

Will close for now.

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

2 participants