What are the correct DesiredCapabilities to run a chrome browser test on an appium node registered with a selenium grid

Support
1

Hello all,
I was wondering how to set up this kind of test if at all possible appium+selenium_grid+chrome_browser.

I’m able to start up the script with Capabilities as follows (without the selenium grid), but unable to get appium working as a node.

deviceName=Android Emulator
platformName=Android
platformVersion=7.1.1
orientation=PORTRAIT
automationName=UIAutomator2
browserName=Chrome

Selenium grid logs:

17:56:28.152 DEBUG - getting the following registration request : {“capabilities”:[{“browserName”:“Chrome”,“version”:“7.1.1”,“maxInstances”:1,“platform”:“ANDROID”}],“configuration”:{“cleanUpCycle”:2000,“timeout”:30000,“proxy”:“org.openqa.grid.selenium.proxy.DefaultRemoteProxy”,“url”:“http://127.0.0.1:4724/wd/hub”,“host”:“127.0.0.1”,“port”:4724,“maxSession”:1,“register”:true,“registerCycle”:5000,“hubPort”:4444,“hubHost”:“127.0.0.1”,“id”:“http://127.0.0.1:4724”}}
17:56:28.170 DEBUG - Using class org.openqa.grid.selenium.proxy.DefaultRemoteProxy
17:56:28.171 DEBUG - starting cleanup thread
17:56:28.173 INFO - Registered a node http://127.0.0.1:4724
17:56:28.173 DEBUG - cleanup thread starting…
17:56:28.173 WARN - Cleaning up stale test sessions on the unregistered node http://127.0.0.1:4724
17:56:28.174 DEBUG - proxy added http://127.0.0.1:4724
17:56:28.174 DEBUG - Available nodes: [http://127.0.0.1:4724]
17:56:28.177 DEBUG - Trying to create a new session on node http://127.0.0.1:4724
17:56:28.184 INFO - Trying to create a new session on test slot {browserName=Chrome, maxInstances=1, version=7.1.1, platform=ANDROID}
17:56:28.186 DEBUG - Closing connections idle longer than 100 MILLISECONDS
17:56:28.189 DEBUG - CookieSpec selected: default
17:56:28.196 DEBUG - Auth cache not set in the context
17:56:28.197 DEBUG - Connection request: [route: {}->http://127.0.0.1:4724][total kept alive: 0; route allocated: 1 of 2000; total allocated: 1 of 2000]
17:56:28.200 DEBUG - Connection leased: [id: 13][route: {}->http://127.0.0.1:4724][total kept alive: 0; route allocated: 2 of 2000; total allocated: 2 of 2000]
17:56:28.206 DEBUG - Opening connection {}->http://127.0.0.1:4724
17:56:28.206 DEBUG - Connecting to /127.0.0.1:4724
17:56:28.246 DEBUG - http-outgoing-12: Shutdown connection
17:56:28.247 DEBUG - Connection discarded
17:56:28.255 DEBUG - Connection released: [id: 12][route: {}->http://127.0.0.1:4724][total kept alive: 0; route allocated: 1 of 2000; total allocated: 1 of 2000]
17:56:28.255 DEBUG - Failed to check status of node: Connect to 127.0.0.1:4724 [/127.0.0.1] failed: Connection refused: connect

Any help and ideas are much appreciated.
Thanks!

2

may this helps:-

http://appium.io/docs/en/advanced-concepts/grid/

3

Hi, thanks for your suggestion.

Acutally that’s not exactly what I am asking about. I’m able to run native apps on appium through the grid / without one.
What I’m trying to do here is to have the Chrome browser open on the mobile device (or an emulator) and then run a regular chromedriver driven web test.

Again, in a mobile device, in the browser, running on an Appium node registered on a Selenium grid.

Thanks!