I am not sure if there is a reason that the SpecFlow.Actions.WindowsAppDriver.WindowsAppDriverOptions disallows any additional capabilities besides app, but it would be useful to be able to add other capabilities to be picked up by Appium.
In my case, I need to be able to set some application arguments (i.e. the Appium appArguments).
I think I had the wrong base branch set in the PR at first, but I changed it... so now there should be no conflicts. Not sure how I can force the checks to run again...
I am not sure if there is a reason that the
SpecFlow.Actions.WindowsAppDriver.WindowsAppDriverOptions
disallows any additional capabilities besidesapp
, but it would be useful to be able to add other capabilities to be picked up by Appium.In my case, I need to be able to set some application arguments (i.e. the Appium
appArguments
).See: https://github.com/appium/appium-windows-driver#windowsdriver-specific-capabilities