Skip to main content

Appium Testing - Real Device On HyperExecute

This page outlines how to execute your Appium tests on HyperExecute using TestNG with YAML 0.2

HyperExecute uses YAML 0.2 to perform the tests using Appium.

Prerequisites​

To run the Tests on HyperExecute from your Local System, you are required:

Sample repo

All the code samples in this documentation can be found on LambdaTest's Github Repository. You can either download or clone the repository to quickly run your tests. Image View on GitHub

If you do not have any .apk or .ipa file, you can run your sample tests on LambdaTest by using our sample 🔗 Android app or sample 🔗 iOS app.

Download HyperExecute CLI​

The HyperExecute CLI is used for triggering tests on HyperExecute. It is recommend to download the HyperExecute CLI binary on the host system to perform the tests on HyperExecute. The CLI download site for various platforms is displayed below:

PlatformHyperExecute CLI download location
Windowshttps://downloads.lambdatest.com/hyperexecute/windows/hyperexecute.exe
macOShttps://downloads.lambdatest.com/hyperexecute/darwin/hyperexecute
Linuxhttps://downloads.lambdatest.com/hyperexecute/linux/hyperexecute

Setup Environment Variable​

Export the environment variables LT_USERNAME and LT_ACCESS_KEY that are available in the LambdaTest Profile page. Run the below mentioned commands in the terminal to setup the CLI and the environment variables.

export LT_USERNAME="YOUR_LAMBDATEST_USERNAME"
export LT_ACCESS_KEY="YOUR_LAMBDATEST_ACCESS_KEY"

Steps to Run Your Test​

Step 1: Upload your Application​

Upload your iOS application (.ipa file) or android application (.apk file) to the LambdaTest servers using our REST API. You need to provide your Username and AccessKey in the format Username:AccessKey in the cURL command for authentication. Make sure to add the path of the appFile in the cURL request. Here is an example cURL request to upload your app using our REST API:

curl -u "YOUR_LAMBDATEST_USERNAME:YOUR_LAMBDATEST_ACCESS_KEY" --location --request POST 'https://manual-api.lambdatest.com/app/upload/realDevice' --form 'name="Android_App"' --form 'appFile=@"<RELATIVE_PATH_OF_YOUR_APP>"' 

Response of above cURL will be a JSON object containing the App URL of the format - lt://APP123456789123456789 and will be used in the next step.

Step 2: Configure your Test Script​

Write Your Automation Script in the client language of your choice from the ones supported by Appium. An automation script for the sample applications have been provided below.

Here is a sample automation script in Java for the sample app downloaded above. Ensure to update the app_url, username and accesskey in the below code.

AndroidApp.java
import io.appium.java_client.AppiumDriver;
import io.appium.java_client.MobileBy;
import io.appium.java_client.MobileElement;
import io.appium.java_client.android.AndroidElement;
import org.openqa.selenium.remote.DesiredCapabilities;
import org.openqa.selenium.support.ui.ExpectedConditions;
import org.openqa.selenium.support.ui.WebDriverWait;
import org.testng.annotations.Test;

import java.net.URL;
import java.util.List;

public class AndroidApp {

public static String userName = System.getenv("LT_USERNAME");
public static String accessKey = System.getenv("LT_ACCESS_KEY");

public String gridURL = "@mobile-hub.lambdatest.com/wd/hub";

AppiumDriver driver;

@Test
@org.testng.annotations.Parameters(value = {"device", "version", "platform"})
public void AndroidApp1(String device, String version, String platform) {
version = System.getProperty("platformVersion");
try {
DesiredCapabilities capabilities = new DesiredCapabilities();
capabilities.setCapability("build","Java TestNG Android");
capabilities.setCapability("name",platform+" "+device+" "+version);
capabilities.setCapability("deviceName", device);
capabilities.setCapability("platformVersion",version);
capabilities.setCapability("platformName", platform);
capabilities.setCapability("isRealMobile", true);
//AppURL (Create from Wikipedia.apk sample in project)
capabilities.setCapability("app", "lt://proverbial-android"); //Enter your app url
capabilities.setCapability("deviceOrientation", "PORTRAIT");
capabilities.setCapability("console", true);
capabilities.setCapability("network", false);
// capabilities.setCapability("visual", true);
capabilities.setCapability("devicelog", true);
//capabilities.setCapability("geoLocation", "HK");

String hub = "https://" + userName + ":" + accessKey + gridURL;
driver = new AppiumDriver(new URL(hub), capabilities);

MobileElement color = (MobileElement) driver.findElementById("com.lambdatest.proverbial:id/color");
//Changes color to pink
color.click();
Thread.sleep(1000);
//Back to orginal color
color.click();

MobileElement text = (MobileElement) driver.findElementById("com.lambdatest.proverbial:id/Text");
//Changes the text to "Proverbial"
text.click();

//toast will be visible
MobileElement toast = (MobileElement) driver.findElementById("com.lambdatest.proverbial:id/toast");
toast.click();

//notification will be visible
MobileElement notification = (MobileElement) driver.findElementById("com.lambdatest.proverbial:id/notification");
notification.click();
Thread.sleep(2000);

//Opens the geolocation page
MobileElement geo = (MobileElement) driver.findElementById("com.lambdatest.proverbial:id/geoLocation");
geo.click();
Thread.sleep(5000);

//takes back to home page
MobileElement home = (MobileElement) driver.findElementByAccessibilityId("Home");
home.click();

//Takes to speed test page
MobileElement speedtest = (MobileElement) driver.findElementById("com.lambdatest.proverbial:id/speedTest");
speedtest.click();
Thread.sleep(5000);

MobileElement Home = (MobileElement) driver.findElementByAccessibilityId("Home");
Home.click();

//Opens the browser
MobileElement browser = (MobileElement) driver.findElementByAccessibilityId("Browser");
browser.click();

MobileElement url = (MobileElement) driver.findElementById("com.lambdatest.proverbial:id/url");
url.sendKeys("https://www.lambdatest.com");

MobileElement find = (MobileElement) driver.findElementById("com.lambdatest.proverbial:id/find");
find.click();

driver.quit();

} catch (Exception e) {
e.printStackTrace();
try{
driver.quit();
}catch(Exception e1){
e.printStackTrace();
}
}


}
}

Step 3: Update your XML file​

Create .XML file in order to run your test and define device capabilities. Please find sample code below for the same.

android-parallel.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
<suite thread-count="100" name="Mobile" parallel="tests">

<test name="AndroidAppTest_1">
<parameter name="version" value="11" />
<parameter name="platform" value="Android" />
<parameter name="device" value="Galaxy Note20 Ultra 5G" />
<classes>
<class name="AndroidApp" />
</classes>
</test>

<test name="AndroidAppTest_2">
<parameter name="version" value="12" />
<parameter name="platform" value="Android" />
<parameter name="device" value="Galaxy S22 5G" />
<classes>
<class name="AndroidApp" />
</classes>
</test>

<test name="AndroidAppTest_3">
<parameter name="version" value="13" />
<parameter name="platform" value="Android" />
<parameter name="device" value="Galaxy S21 Ultra 5G" />
<classes>
<class name="AndroidApp" />
</classes>
</test>

<test name="AndroidAppTest_4">
<parameter name="version" value="11" />
<parameter name="platform" value="Android" />
<parameter name="device" value="Galaxy S20" />
<classes>
<class name="AndroidApp" />
</classes>
</test>

<test name="AndroidAppTest_5">
<parameter name="version" value="12" />
<parameter name="platform" value="Android" />
<parameter name="device" value="Galaxy S21 5G" />
<classes>
<class name="AndroidApp" />
</classes>
</test>
</suite>

Step 4: Configure YAML and Execute your Script​

android-parallel.yaml
version: 0.2
globalTimeout: 150
testSuiteTimeout: 150
testSuiteStep: 150

runson: linux

concurrency: 5

autosplit: true

retryOnFailure: false
maxRetries: 1

pre:
- mvn -Dmaven.repo.local=./.m2 dependency:resolve

appium: true
framework:
name: maven/testng
defaultReports: false
discoveryType: xmltest
flags: ["-Pandroid-parallel"]

jobLabel: ['HYP-RD', 'Android', 'Multiple Device']

The region parameter specifies the region or location where the Appium tests will be executed. Our platform supports the following three regions:

  • ap (Asia-Pacific)
  • us (United States)
  • eu (European Union)

Step 5: Execute your Test Suite​

NOTE : In case of MacOS, if you get a permission denied warning while executing CLI, simply run chmod u+x ./hyperexecute to allow permission. In case you get a security popup, allow it from your System Preferences → Security & Privacy → General tab.

Run the below command in your terminal at the root folder of the project:

./hyperexecute --config RELATIVE_PATH_OF_YOUR_YAML_FILE

OR use this command if you have not exported your username and access key in the step 2.

./hyperexecute --user YOUR_LAMBDATEST_USERNAME --key YOUR_LAMBDATEST_ACCESS_KEY --config RELATIVE_PATH_OF_YOUR_YAML_FILE 

Configure Smart UI​

To configure SmartUI with HyperExecute, you need to simply add a capability in your test file:

"smartUI.project": "<YOUR_SMARTUI_PROJECT_NAME>"

Refer to the Automation Capabilities Generator to understand how to write the capability in different languages.

automation-dashboard

More About Desired Capabilities​

Sample Capabilities for both android and iOS are mentioned below -

{
"deviceName": "Galaxy Tab S4",
"platformName": "android",
"platformVersion": "10",
"app": "App_url",
"visual": True,
"console": True,
"deviceOrientation": "PORTRAIT",
"build": "new-12",
"isRealMobile": True,
}

For more details, please refer to our guide on Desired Capabilities in Appium.

Every test run on the HyperExecute has a unique jobId associated with it. Each jobId can in turn constitute single (or multiple) groupId(s). You can visit HyperExecute automation dashboard for checking the status of the test execution.

The snapshot below shows how to navigate to the respective testID for viewing the Selenium logs:

automation-dashboard

Test across 3000+ combinations of browsers, real devices & OS.

Book Demo

Help and Support

Related Articles