Remove restrictions on browserName and combining with app capability for Grid #139
This is the android implementation of appium/appium-ios-driver#127, which has already been merged.
This PR also had to remove the specific check for providing
I've tested these changes with Appium v1.5 locally and with Selenium Grid 2.52.0.
… grid This restriction broke compatibility with Selenium Grid where the browserName capability is used to define the node's available simulator/devices. Also remove/modify tests that are affected.
Sorry guys, I just pushed again. I decided to change the existing unit test to specifically check that this case does pass, so it doesn't break in the future.
Just curious, is SauceLabs using Selenium Grid? Since most of the Appium maintainers seem to work for Sauce, I'm wondering if it's actually getting tested in this way.