Selecting a single cloud device during execution
From within your action lines, you can control which cloud device your test is to execute on. The built-in assign cloud device action is used to specify a target cloud device upon which the subsequent action lines are to be run.
To start automated mobile web testing on a cloud device in a given WebDriver based cloud service, declare the following action lines in your test:
Use the assign cloud device built-in action to define a list of desired capabilities, which are sets of keys and values sent to the Appium server in JSON format.
Note:- See the Desired Capabilities documentation for the list of capabilities available for Appium.
- Along with the capabilities of Appium, some WebDriver based cloud services might have their own set of capabilities. For example, Testdroid, several additional Testdroid Desired Capabilities are also provided (learn more). Also ensure that your Testdroid Cloud project’s type must be either Appium Android client side or Appium iOS client side
For example: You’d like to automate mobile web application testing on Chrome in Testdroid.
Your set of desired capabilities should be defined as follows.
- For specific Testdroid capabilities:
- testdroid_username: Email registered at Testdroid Cloud. Example: [email protected].
- testdroid_password: Password for your Testdroid Cloud account. Example: p4s$w0rd
- testdroid_target: Target test type. Example: chrome, which invokes Google Chrome browser during mobile web application testing.
- testdroid_project: Project name that will be displayed on Web UI. Example:
Chrome Android Project
. - testdroid_testrun: Name given to each Test Run under a Project. Example: Test Run 1.
- testdroid_device: The device name that uniquely identifies a device on Testdroid Cloud. Example: Sony Xperia Z C6603.
- For Appium server capabilities:
- deviceName: The kind of mobile device to use. For example: Android Device
- platformName: Which mobile OS platform to use. For example: Android
- browserName: Name of mobile web browser to automate. For example: chrome
- Your JSON string is as follows:
{"deviceName":"Android Device", "platformName":"Android", "browserName":"chrome", "testdroid_username": "[email protected]", "testdroid_password": "p4s$w0rd", "testdroid_target": "chrome", "testdroid_project": " `Chrome Android Project`", "testdroid_testrun": "Test Run 1", "testdroid_device": "Sony Xperia Z C6603"
- For specific Testdroid capabilities:
Specify URL Appium server of the given WebDriver based cloud service. For example: Testdroid, the URL Appium server is http://appium.testdroid.com/wd/hub
assign device should resemble the following.
url capability name assign cloud device http://appium.testdroid.com/wd/hub {"deviceName":"Android Device", Xperia Z "platformName":"Android", "browserName":"chrome", "testdroid_username": "[email protected]", "testdroid_password": "p4s$w0rd", "testdroid_target": "chrome", "testdroid_project": " `Chrome Android Project`", "testdroid_testrun": "Test Run 1", "testdroid_device": "Sony Xperia Z C6603"}
Make a connection to the target cloud device via the connect cloud device built-in action, as specified by its logical name.
Note:The name is established in advance by the assign cloud device action, which assigns a logical name to a mobile cloud device.name session id connect cloud device Xperia Z >>Xperia_Z_sessionID
Employ the use cloud device built-in action to use the cloud device to initiate automated tests. The invoked cloud device is specified by its session ID.
Note:The session ID specified in the session id argument is retrieved via the connect cloud device action.session id use cloud device #Xperia_Z_sessionID
Now, you’re ready to begin performing your automated web-based tests on the target cloud device.
When you no longer need to continue the tests on the target cloud device, it is highly recommended that you terminate the connection with the target device by using the disconnect cloud device built-in action.
session id disconnect cloud device #Xperia_Z_sessionID
When you’d like to switch back to the host machine to continue the remaining tests, use the use host machine built-in action.
Overall, your snippet of test should resemble the following.
//Define desired capabilities url capability name assign cloud device http://appium.testdroid.com/wd/hub {"deviceName":"Android Device", Xperia Z "platformName":"Android", "browserName":"chrome", "testdroid_username": "[email protected]", "testdroid_password": "p4s$w0rd", "testdroid_target": "chrome", "testdroid_project": " `Chrome Android Project`", "testdroid_testrun": "Test Run 1", "testdroid_device": "Sony Xperia Z C6603"} //Connect to the target cloud device name session id connect cloud device Xperia Z >>Xperia_Z_sessionID //Use the target cloud device session id use cloud device #Xperia_Z_sessionID //Implement action lines to perform automated mobile web-based testing //Disconnect the target device session id disconnect cloud device #Xperia_Z_sessionID