Situations where you may not want to supply a browserName

[Topperfalkon]

So, I'm not sure how common this is, but playing around with Nightwatch 1.7.8 at the moment, and we're investigating whether we can use it to test mobile apps via Appium, as Appium is Webdriver compatible.

Understandably, Nightwatch is geared more towards web automation, but we feel there's a potential benefit to be able to use the same overall framework across all teams and all devices. Unfortunately, Appium seems to throw a hissy fit if you try and specify a browserName and an appPackage, particularly for working with Android

I'm looking at Appium 1.21.0 on Windows.

I've managed to get it working by patching my local nightwatch install to not set firefox as default browser, which is the current behaviour if no browserName is defined

[beatfactor]

Have you tried setting browserName to null?

There's a guide on using Appium with Android on (https://github.com/nightwatchjs/nightwatch/wiki/Testing-Android-native-application-and-mobile-browsers-with-Appium)[our wiki], though it's probably a bit outdated. Feel free to open a new issue or send a PR with changes needed to get it working.

We're also working on a documentation page for Appium with some examples for our website.

[Topperfalkon]

Ah, yeah. I did try that, but I believe there's a bug. I'll raise an issue and I believe I've got a fix for it that I can PR shortly