Scope :

This document details the steps required to enable your Appium or Selenium scripts to run on the Appachhi Platform.

Steps :


There are various build tools available out there in the market like Ant, Maven, Gradle, CMake, Groovy and also TestNG itself. But as per our current implementation of Appachhi platform, we recommend you to use either Maven or Gradle as build tools for your appium/selenium test scripts.


Make sure you have defined at least one testng xml anywhere in your Script. We make use of TestNG xml to recognize what is your testing scope, which package/class/test/method you want to run on our platform.

Here’s a sample TestNG code for reference

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "">
<suite name="SuiteName">
    <test name="Test Case 1">
      <class name=""/>
    <test name="Test Case 2" thread-count="1">
      <package name=""/>

And also a snapshot of how your selection will be shown in our platform

image of platform selector

For detailed reference on declaring your TestNG xml, please refer following link.


Appachhi requires control over few of the components in the scripts like Device ID, Selenium/Appium Hub URL, Application path, Screenshot path etc. Below are the different ways to set your capabilities.

  1. Hardcode - desiredCapabilities.setBrowserName(“Safari”);

  2. Set using TestNG Parameter -

    Define parameters in your TestNG xml and utilize them in your scripts using @Parameters annotation.

  3. Using config properties like, pom.xml or even your custom config.ini file.

  4. Using command line system properties accessed via System.getProperty(“property_index”)

Appachhi expects all the below mentioned parameters are read in your scripts as command-line system properties and configure them accordingly.

Ex: # Define the desired capability for browser as String browser = System.getProperty(browser); DesiredCapabilities caps = new DesiredCapabilities(); caps.setBrowserName(browser); mvn -Dbrowser="chrome" test

This will help us to control all the desired capabilities via command line


Some of the desired capabilities that should be defined without fail include:

  1. Native Android/iOS App

    1. Device serial ID
    2. mobile_udid - (Ex: -Dmobile_udid=CSDWUJ652JK)

      Usage - caps.setCapability("udid",System.getProperty("mobile_udid"));

    3. Appium/Selenium Hub URL
    4. appium_url - (Ex: appium_url=

      Usage - new AppiumDriver(new URL(System.getProperty( "appium_url")), caps);

    5. Application Path (apk/ipa)
    6. app_file_path - (Ex: app_file_path=D:\User\admin\apks\sample.apk or /Users/admin/Downloads/sample.ipa)


      # Read path of the apk/ipa using command line system property File app = new File(System.getProperty(“app_file_path”));

      # Set the capability using the absolute local path to the apk/ipa caps.setCapability("app", app.getAbsolutePath());

    7. Screenshot path - Path to where the screenshots to be stored for each click
    8. screenshot_path - (Ex: screenshot_path=D:\User\Script\screenshots)


      TakesScreenshot source = ((TakesScreenshot) driver);
      TakesScreenshot source = ((TakesScreenshot) driver);
      File SrcFile = source.getScreenshotAs(OutputType.FILE);
      File DestFile = new File( System.getProperty(“screenshot_path”)+File.separator+screenshot_name +".jpg");
      FileUtils.copyFile(SrcFile, DestFile);

    9. Environment
    10. environment - (Ex: environment=PROD/TEST/LIVE )

      Usage - Although this might not be required in everyone’s case, but if you have written scripts which behaves differently for live environment and test environment, you can make use of this property to differentiate between them, else you can completely ignore this. This is provided to your script from Appachhi platform using the TestRun creation form.

      testplan details screenshot
    11. Channel
    12. channel - ( Ex: ANDROID/IOS)

      Usage - Again, this depends on the scenario, if you have written single script to cater multiple platforms like ANDROID/IOS, you need to read this system property and switch between platforms. Else, you can just ignore it.

    13. Platform version ( device OS version )
    14. platform_version - ( Ex: platform_version=6.0/7.1.1,11.4 etc.. )


      caps.setCapability(MobileCapabilityType.PLATFORM_VERSION, System.getProperty("platform_version"));

    15. Device name
    16. device_name - ( Ex: device_name=Google Nexus 5s/ iPhone 5s )


      caps.setCapability(MobileCapabilityType.DEVICE_NAME, System.getProperty("device_name"));

  2. Android / iOS Mobile Web

    1. Device serial ID - [Refer 4.a]
    2. Appium/Selenium Hub URL - [Refer 4.a]
    3. Screenshot path - [Refer 4.a]
    4. Browser Name
    5. browser - ( Ex: browser=chrome/safari )

      Usage - Indicates which browser to launch the mobile web test on.

      caps.setCapability(MobileCapabilityType.BROWSER_NAME, System.getProperty("browser"));

    6. Channel
    7. channel - ( Ex: ANDROID_MWEB/IOS_MWEB)

    8. Web Application URL
    9. app_browser_url - ( Ex: app_browser_url= )

      Usage - Indicates URL of the web application to run scripts on.

    10. Environment - [Refer 4.a]
  3. Desktop Web

    1. Web Application URL - [Refer]
    2. Screenshot path - [Refer 4.a]
    3. Browser Resolution - Indicates the resolution of the browser in concern
    4. Refer screenshot to know how the resolution will be selected on Appachhi platform

      select resolution screenshot

      browser_resolution_width - ( Ex: browser_resolution_width=1024 )

      browser_resolution_height - ( Ex: browser_resolution_height=768 )


      Dimension resolution = new

    5. Browser Version - Desktop browser version to be set
    6. browser_version - ( Ex: browser_version=64.1 )



    7. Browser Binary File path - Browser installation path
    8. browser_bin_path - ( Ex: browser_bin_path = D:\User\admin\browsers\Chrome\chrome64.exe or /Applications/Google\\ Chrome )


      System.setProperty("", System.getProperty( "browser_bin_path"));
      System.setProperty("webdriver.firefox.bin", System.getProperty( "browser_bin_path"));

      Again configuration depends on browser property.

    9. Browser WebDriver Path - Path where browser driver is located
    10. browser_driver_path - ( Ex: browser_driver_path = D:\User\admin\browsers\drivers\geckodriver.exe or /Users/admin/Downloads/drivers/geckodriver )


      System.setProperty("", System.getProperty( "browser_driver_path"));
      System.setProperty("webdriver.gecko.driver", System.getProperty( "browser_driver_path"));

    11. Channel
    12. channel - ( Ex: DESKTOP_WEB)

    13. Environment - [Refer 4.a]


One recommendation is to Implement Assertions at the test level instead of page level with proper log messages. This will enable you to have rich test centric logs to debug in case of failures.