Adding Appium to the list of Drivers

[lfarnell]

I've started using your library for a project of mine and was wondering if you would be interest in a pull request for adding Appium drivers to the list.

[bonigarcia]

Sure, PR's are welcome!

Please provide JUnit tests with your code in order to assess the new feature. Thank you!

[bonigarcia]

Did you manage to add Appium to the driver list?

[lfarnell]

@bonigarcia not yet but i'm hopeful to do so in the next little bit

[rosolko]

@bonigarcia @lfarnell I used appium for some time. Appium works with own server (like selenium server standalone) and we don't need to store and add some variables to PATH. I formed the opinion that we should't implement this type of driver. All of because from site(bitbucket) installs old version of appium server and GUI. And really latest version installs from node. From my point of view, the implementation of this functionality useless.

[bonigarcia]

I've reviewed Appium and @rosolko has a point.

@lfarnell Could you explain to us what is your idea for supporting Apium in WebDriverManager?

[lfarnell]

cc @bonigarcia @rosolko

Your point merely only says it shouldn't be implemented because BitBucket has old version's of Appium. I personally think that by incorporating Appium into the list, user's can have a seamless experience starting the Appium server and mobile tests simultaneously rather then having to start another process and ensuring that it's running before executing tests. That in itself seems very problematic.

For the dependency on node.js for "newer" verisons of Appium, I dont see why you can't say node.js will be a dependency if you want to run Appium. Plenty of tools and libraries require dependencies.

[bonigarcia]

As Linus Torvalds said: "Talk is cheap. Show me the code".

[rosolko]

@lfarnell But on other hand - archive from bitbucket contains installer, not a driver(like chromedriver) that using like a bridge. In this case tool didn't manage webdrivers.

[bonigarcia]

This issue seems to be abandoned. Closing.