Connecting appium server to selenium grid for android

Has anyone tried using cucumber-jvm/junit/spring to run parallel tests? I have an existing framework that i would like to enhance with parallel test capability.

Hello,

  I successfully configured my selenium grid with appium. I successfully created to driver for two different android devices . Lets say d1 and d2 . now i want to maintain sink in between them means my driver does some operation using d1 and then after completing that another operation on driver d2. When i am doing operation on d2 another driver d1 should be ideal
  But when i am doing operation on 2nd driver then on first device the app is in background after switching to first device

it gives me error that session is not valid.please help me out here, what should i do? should i implement multi-threading ? or is there any way to put first driver on ideal state while second is doing that operation ?

Has anyone managed to distribute the tests across available devices? This is a native grid functionality, but it doesnt seem to work well with Appium (as you can only run one device per session). A solution, preferably in java, would be helpful - or pointers, I am looking into it myself but seem to be stuck.

@Appium_Master @Arvind_Patel am trying to run a appium script in Two devices [ Node 1(nexus ) , Node 2(Sony) ] in MAC using Selenium Grid concept

I have done the following
1) Created a Hub by using
java -jar selenium-server-standalone-2.45.0.jar -role hub
2) Triggered the nodes as below
NEXUS Device:
node /Applications/Appium.app/Contents/Resources/node_modules/appium/bin/appium.js -a 192.168.1.120 -p 3482 --nodeconfig "/Users/mobilecoe/Desktop/Karthik/Selenium Grid/Nexusin3482.json" --udid 05cd6a0af0ddb24e

Sony Xperia :

node /Applications/Appium.app/Contents/Resources/node_modules/appium/bin/appium.js -a 192.168.1.120 -p 4723 --nodeconfig "/Users/mobilecoe/Desktop/Karthik/Selenium Grid/Sonyin3483.json" --udid BX903K4MC3

Please find below my script and TestNG file

package com.cognizant.grid;

import java.net.MalformedURLException;
import java.net.URL;

import io.appium.java_client.AppiumDriver;
import io.appium.java_client.android.AndroidDriver;
import io.appium.java_client.remote.MobileCapabilityType;

import org.openqa.selenium.By;
import org.openqa.selenium.remote.DesiredCapabilities;
import org.openqa.selenium.remote.RemoteWebDriver;
import org.testng.annotations.AfterMethod;
import org.testng.annotations.BeforeMethod;
import org.testng.annotations.Parameters;
import org.testng.annotations.Test;

public class SeleniumGrid_mobile {
 AppiumDriver driver;	
@Parameters({"browserName","platform","deviceName","version"})	
@BeforeMethod
public void beforeMethod(String browserName, String platform, String deviceName, String version ) throws MalformedURLException{
	
	
	
	   DesiredCapabilities capabilities = DesiredCapabilities.android();
	   capabilities.setCapability("browserName", browserName);
	   capabilities.setCapability("platform", platform);
	   capabilities.setCapability("deviceName", deviceName);
	   capabilities.setCapability("version", version);
	   
	   
	   //capabilities.setCapability(MobileCapabilityType.AUTOMATION_NAME,"Appium");
	   
	   driver   = new AndroidDriver(new URL("http://localhost:4444/wd/hub"), capabilities);
	
	
}
@Test
public void myTest() throws InterruptedException{
	
	System.out.println("inside");
    driver.get("http://gmail.com/");
    Thread.sleep(2000);
    driver.findElement(By.id("Email")).sendKeys("avkkkkkkkk");
    Thread.sleep(5000); 
	
}

@AfterMethod()
public void afterMethod(){
	
	driver.quit();
}

	
}

And my TestNG xml file is

<?xml version="1.0" encoding="UTF-8"?>
<suite name="Selenium Grid" verbose="1" >
  <test name="SeleniumGrid_Sony" >
     
     <parameter name="browserName" value="Chrome"/>
     <parameter name="platform" value="Android"/>
     <parameter name="deviceName" value="BX903K4MC3"/>
     <parameter name="version" value="4.3"/>
      
    <classes>
      <class name="com.cognizant.grid.SeleniumGrid_mobile"/>
      
    </classes>
 </test>
 
  <test name="SeleniumGrid_Nexus" >
     
     <parameter name="browserName" value="Chrome"/>
     <parameter name="platform" value="Android"/>
     <parameter name="deviceName" value="05cd6a0af0ddb24e"/>
     <parameter name="version" value="5.0"/>
      
    <classes>
      <class name="com.cognizant.grid.SeleniumGrid_mobile"/>
      
    </classes>
 </test>
</suite>

I am getting the an message as below in the Hub

19:48:42.887 INFO - Got a request to create a new session: Capabilities [{platform=ANDROID, deviceName=BX903K4MC3, platformName=Android, browserName=Chrome, version=4.3}]
19:48:43.061 INFO - Got a request to create a new session: Capabilities [{platform=ANDROID, deviceName=05cd6a0af0ddb24e, platformName=Android, browserName=Chrome, version=5.0}]

But the script is not getting triggered and it shows as

==============================================
Selenium Grid
Total tests run: 2, Failures: 0, Skips: 2
Configuration Failures: 2, Skips: 2
===============================================

org.openqa.selenium.WebDriverException: Error forwarding the new session cannot find : Capabilities [{platform=ANDROID, deviceName=BX903K4MC3, platformName=Android, browserName=Chrome, version=4.3}]
Command duration or timeout: 248 milliseconds
Build info: version: '2.45.0', revision: '32a636c', time: '2015-03-05 22:01:35'
System info: host: 'MobileCoes-MacBook-Pro.local', ip: '192.168.1.120', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.9.4', java.version: '1.7.0_55'
Driver info: io.appium.java_client.android.AndroidDriver
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
	at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:204)
	at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:156)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:599)
	at io.appium.java_client.AppiumDriver.execute(AppiumDriver.java:180)
	at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:240)
	at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:126)
	at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:153)
	at io.appium.java_client.AppiumDriver.<init>(AppiumDriver.java:109)
	at io.appium.java_client.android.AndroidDriver.<init>(AndroidDriver.java:39)
	at com.cognizant.grid.SeleniumGrid_mobile.beforeMethod(SeleniumGrid_mobile.java:35)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84)
	at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564)
	at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213)
	at org.testng.internal.Invoker.invokeMethod(Invoker.java:653)
	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
	at org.testng.TestRunner.privateRun(TestRunner.java:767)
	at org.testng.TestRunner.run(TestRunner.java:617)
	at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
	at org.testng.SuiteRunner.run(SuiteRunner.java:240)
	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224)
	at org.testng.TestNG.runSuitesLocally(TestNG.java:1149)

Can you please help me on this ?

I am getting a

org.openqa.selenium.WebDriverException: Error forwarding the new session cannot find : Capabilities [{platform=ANDROID, platformName=Android, browserName=Chrome, applicationName=BX903K4MC3, version=4.3}]

I have connected 2 Android devices one with version 4.3 and another in version 5.0
with device name as BX903K4MC3 & 05cd6a0af0ddb24e

Am I missing some configuration ??? can @Appium_Master , @Arvind_Patel , @Hassan_Radi or any other can help me on this ?

It should be "deviceName" not "applicationName".

Hi , Based on the some of the earlier post in this page i have changed to applicationName from deviceName , after this now one device [ first device in adb devices list ] alone is getting executed in the grid

  17:29:22.432 INFO - Got a request to create a new session: Capabilities [{automationName=Appium, platform=ANDROID, deviceName=BX903K4MC3, platformName=Android, browserName=Chrome, version=4.3}]
17:29:22.626 INFO - Got a request to create a new session: Capabilities [{automationName=Appium, platform=ANDROID, deviceName=05cd6a0af0ddb24e, platformName=Android, browserName=Chrome, version=5.0}]
17:29:22.626 INFO - Available nodes: [host :http://127.0.0.1:4723, host :http://127.0.0.1:4725]
17:29:22.626 INFO - Trying to create a new session on node host :http://127.0.0.1:4723
17:29:22.627 INFO - Trying to create a new session on test slot {platform=ANDROID, browserName=Chrome, maxInstances=3, applicationName=05cd6a0af0ddb24e, version=5.0}
17:29:24.406 WARN - Failed to check status of node: server response code : 500

I am getting an error message as check status of node failed for the second node

As the documentation mentions65, you have to use different
server arguments for the following:

-p the main Appium port
-U the device id
-bp the Appium bootstrap port
--chromedriver-port the chromedriver port (if using webviews or chrome)
--selendroid-port

Hi all,

I'm getting below error while connecting to Grid using Appium , the second device getting error and one device is executing fine.

error: Unhandled error: Error: read ECONNRESET
at errnoException (net.js:905:11)
at TCP.onread (net.js:559:19) context: [POST /wd/hub/session {"desiredCapabilities...

Error Coming while running multiple sessions using appium.Please let me know if any one knows about this.

I'm using different ports 4723, 4724 for two devices.

Thanks,
Bhaskar.

Hi @Appium_Master @Arvind_Patel @rgonalo @Hassan_Radi . Now I am able to run my test case parallely and sequentially for Android devices

I will post all the steps below to run the scripts parallely

1) START THE HUB

java -jar selenium-server-standalone-2.45.0.jar -role hub -hub http://xxxxxxxxx:4444/grid/register

2) START THE APPIUM NODE
FIRST DEVICE :
node /Applications/Appium.app/Contents/Resources/node_modules/appium/bin/appium.js -a 192.168.1.109 -p 4723 --nodeconfig "/Users/mobilecoe/Desktop/Karthik/Selenium Grid/Nexusin4723localwithmachineIP.json" --udid xxxxxxxxxxxxx --bootstrap-port 2252 --chromedriver-port 4735

SECOND DEVICE:

node /Applications/Appium.app/Contents/Resources/node_modules/appium/bin/appium.js -a 192.168.1.109 -p 4725 --nodeconfig "/Users/mobilecoe/Desktop/Karthik/Selenium Grid/Sonyin4725localusingMachineIP.json" --udid xxxxxxxxx --bootstrap-port 2251 --chromedriver-port 4733

NOTE: I am using Mac

3) Create the TestNG project with the xml setting pointing the desired capabilities

<?xml version="1.0" encoding="UTF-8"?>
<suite name="Selenium Grid" parallel="none" thread-count="2" verbose="1" >
  
     <test name="SeleniumGrid_Sony" >
     
     <parameter name="browserName" value="Chrome"/>
     <parameter name="platform" value="Android"/>
     <parameter name="deviceName" value="XXXXXXXXX"/>
     <parameter name="version" value="4.3"/>
     <parameter name="sleep" value="1000"/>
    <classes>
      <class name="com.cognizant.grid.SeleniumGrid_mobile"/>
      
    </classes>
 </test>
   <test name="SeleniumGrid_Nexus" >
     
     <parameter name="browserName" value="Chrome"/>
   	<parameter name="platform" value="Android"/>
     <parameter name="deviceName" value="XXXXXXXXXXXXX"/>
     <parameter name="version" value="5.0"/>
     <parameter name="sleep" value="15000"/>
      
    <classes>
      <class name="com.xxxxxx.grid.SeleniumGrid_mobile"/>
      
    </classes>
 </test>
    
 </suite>

And its working fine for me

How to create an Appium Node for Iphone device ?

What are Terminal command line codes to be mentioned for it ? like bootstrap , chromedriver for Android .

@Appium_Master @Hassan_Radi @Arvind_Patel @rgonalo @karthik_holla @Srikanth_Katakam any idea on this ?

@rgonalo
@Hassan_Radi
@Arvind_Patel
@karthik_holla

I have created a separate thread for this discussion but decided to include this question in this thread as it seems to be active.

I need help on running test cases from Selenium Grid server machine running as a hub with the devices connected to the node and here's what I have:

I have a iMac running Mavericks (10.9.5) running Selenium Grid server as a hub. I also have a MacBook Air (running on Mavericks) running Selenium Grid as a node. Appium is running from terminal on port 5000 with --uuid parameter pointing to my iOS device connected to the node.

What works:

If the test cases are on the node, I'm able to run 2 devices in parallel from the node and the node is pointing to the Selenium Gid hub on the iMac.

What I wanted to achieve: (for troubleshooting, I'm only connected to one iOS device on the node).

I would like to have the test cases on the hub machine and this will give me a benefit of having the test scripts in one single location rather than duplicating on each of the nodes. I changed the DesiredCapabilities to point to the node and when I try to instantiate a new IOSDriver, I'm getting a "Session not created error: Bad app: Unable to locate the app". The app is located on the server hub and the path is all correct as I verified from the command line on the server with the stat command and it returns back the .app file. The following is the code that is run from the hub machine:

app = /Volumes/Server/Apps/iOS/SampleApp.app (the sample app is lying on the server from where the following code is running:
File appPath = new File(app);
capabilities.setCapability("app", appPath.getAbsolutePath());
IOSDriver iOSDriver= new IOSDriver (new URL(http://nodeipaddress:5000), capabilities);
The code is throwing exception on the last line when it is trying to instantiate a new IOSDriver.

But, the same code works when run from the node as shown below. Also, the SampleApp.app is lying on the node.
app = /Volumes/Node/Apps/iOS/SampleApp.app
File appPath = new File(app);
capabilities.setCapability("app", appPath.getAbsolutePath());
IOSDriver iOSDriver= new IOSDriver (new URL(http://hubipaddress:4444), capabilities);

I tried the following:
1.changed from getAbsolutePath to getCanonicalPath() and it fails with the same error
2.Changed the path to System.getProperty("user.dir") + "../../Node/Apps/iOS and this doesn't work too.

Ideally, I wanted to keep the test cases in one location and remote execute on the devices connected to the node. Please help.

So, to summarize, when the test cases are run from the hub machine (Machine 1) with the .app lying in a folder on the hub machine, I would like the .app to be installed on the device connected to the node (Machine 2) while the test cases are running from Machine 1.

Thanks.

Anybody?

No matter how I change my code, I'm getting Bad app error (App path needs to be absolute.....blah...blah...blah), when trying to run the code from the hub while the devices are connected to a node (different machine) with appium listening on port 5000 and selenium grid running as a node.

Please help.

Hi @appium_ia,

App capability can be a local path or a remote url (http://appium.io/slate/en/master/?ruby#appium-server-capabilities).
If you have a local path with Selenium Grid, Appium searches the app in the node machine, not in the hub machine.
You should use a remote url or a shared folder path that can be accessed from any node machine.