When considering which approach will work best for you it helps to know more about Appium, the goals of the WinAppDriver project, and some considerations when setting up your test workflow.
When using Appium in the mobile or web world:
Test Runner >> Appium Server >> mobile/web app
When using Appium and testing on Windows:
Test Runner >> Appium Server >> WinAppDriver >> Windows application
When testing Windows apps and not using Appium we just take out the Appium Server:
Test Runner >> WinAppDriver >> Windows application
Appium: http://127.0.0.1:4723/wd/hub
WinAppDriver: http://127.0.0.1:4723
For consistency you can tell WinAppDriver to listen to /wd/hub by passing startup arguments:
winappdriver.exe 127.0.0.1 4723/wd/hub
If you're looking for multi device management, take a look at the Selenium Grid and plan on using Appium to test your Windows devices. Appium supports the Selenium Grid with Windows devices.
If you're running tests for multiple devices, platforms, including browser tests, you should consider using Appium. Appium can make it easier to manage tests across multiple devices.
If you're just testing Windows Apps it's fine to not include Appium
Don't feel like this is a big decision you can't later change - you can experiment, try with and without Appium, and change later if your needs change. Switching between WinAppDriver standalone and using Appium can be near 0 cost, with the bulk of the work dealing with the "wd/hub" difference.
Scott Hanselman's blog post here
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。