Andrew Mills

There is no install needed. WAD has a simple package with a DLL. The "install" is just a copy they do from a root folder. C:\Program Files (x86)\Windows Application Driver...

If you are referring to communicating with its API. then you can build your own, or use appium.

i am confused, if you dont want to communicate with its API, then how are you going to automate?

it sounds like you have a very clear goal in mind, and you blocking out other possibilities. There is no logical reason why you wouldn't hit up its API. if...

For example: Here is some code that will start and stop the process in question. Path : path to the winAppDriver and the executablename is WinAppDriver.exe. Fill in other variables...

There more to the code, but its just to give you a quick understand on how to access the exe.

Appium is an example of a framework that communicates with its API. Do you know about Appium?

A post request to the API to build a new session might look something like this "{\"desiredCapabilities\":{\"app\":\"C:\\\\Program Files (x86)\\\\Google\\\\Chrome\\\\Application\\\\chrome.exe\",\"deviceName\":\"WindowsPC\",\"platformName\":\"Windows\"},\"capabilities\":{\"firstMatch\":[{}]}}" This json body defines how it will load up chrome.exe and...

yes this is by default the host and port you have to connect to. "Windows Application Driver listening for requests at: http://127.0.0.1:4723/"

Well, you won't know until you try it lol but the only concern i see, which i dont think is possible with the winAppDriver, is that the port is being...