Selenium Grid trying to assign Android to Windows machine

Issues/Bugs
1

All nodes are registered correctly on the selenium grid, but somehow Android tests are trying to run on the firefox node. Help?

Here is the basic info for each node:

mac1:
browserName: iPhone
version: 9.0
platform: MAC

mac2:
port: 4725
browserName: Android
version: 9.0
platform: ANDROID

mac2:
port: 4723
browserName: iPhone
version: 9.0
platform: MAC

windows:
port: 5555
browserName: firefox
platform: WINDOWS

Parellel execution Android & IOS with appium using Selenium GRID
2

How are you setting up your desired capabilities object? Paste the code you use to build the object.

3

desired caps for the node, hub, or the android test?

4

Just the capabilities for the Android test should be good enough, but having all 3 sets of capability configurations shown would be helpful too.

5

for the android test my caps are:

platformName = “Android”
platformVersion = “4.4.2”
deviceName = “Galaxy S4”

Should I include “platform”? How does platformName and platform differ?

I’ve already essentially given the node capabilities above. Each uses a json config file. I noticed that the Android test is trying to run on the IOS nodes, also.

6

here’s a log from the hub console:

INFO: REQUEST : {app=[redacted], platformVersion=4.4.2, platformName=Android, deviceName=Galaxy S4}
Apr 20, 2016 4:46:05 PM hudson.plugins.selenium.JenkinsCapabilityMatcher matches
INFO: CURRENT : {browserName=iPhone, maxInstances=1, version=9.0, platform=MAC}
Apr 20, 2016 4:46:05 PM hudson.plugins.selenium.JenkinsCapabilityMatcher matches
INFO: REQUEST : {app=[redacted], platformVersion=4.4.2, platformName=Android, deviceName=Galaxy S4}
Apr 20, 2016 4:46:05 PM org.openqa.grid.internal.TestSlot getNewSession
INFO: Trying to create a new session on test slot {browserName=iPhone, maxInstances=1, version=9.0, platform=MAC}

looking at these logs, i think it might be a problem with “hudson.plugins.selenium.JenkinsCapabilityMatcher”

7

My real issue was not including browserName in my tests’ capabilities. I wasn’t sure if it was required and contradicts some other documentation that says “app” and “browserName” are incompatible. However, when using grid, browserName is required to match with the proper node. After implementing that, I was getting an unrelated error found here:

https://github.com/appium/appium/issues/6412.

The issue lists several workarounds. I’ve opted to downgrade to Appium1.4.16 and it works fine.

Summary:

  • Include browserName capability in test and node (they need to match!)
  • If on Appium 1.5, use a workaround, or downgrade to Appium 1.4.16
8

Ah, that certainly is quite interesting. I use the Selenium standalone package, which uses the DefaultCapabilityMatcher by default. This matcher uses browserName as a criterion for matching, but only if it is present in the capabilities request; since my tests don’t specify browserName, I have not yet run into issues where browserName’s value matters.

9

Yeah, I think it’s possible to match only on platform and version , but it wasn’t working for me.