Docs

Tizen & webOS Hub

Overview

RobusTest supports automated Appium testing for Samsung Tizen and LG webOS smart TV apps through the RobusTest Hub, the same Appium endpoint used for Android and iOS. You point your existing Appium test scripts at the Hub URL and select a Tizen or webOS device through capabilities — no separate framework or SDK is required.

Key Benefits:

  • Real TV Testing: Run tests on actual Samsung Tizen and LG webOS TVs in the device lab
  • Standard Appium Workflow: Uses the same Hub URL and capability model as Appium Hub for Android/iOS
  • CI/CD Ready: Trigger jobs through the Job Payload API using "type": "Appium(App)"

Build Requirements

Upload your app in the package format expected for the platform:

Platform Accepted Formats Notes
Tizen .wgt (web widget) or .tpk (native) Must contain a valid config.xml (.wgt) or tizen-manifest.xml (.tpk) with the app ID, package, and version. RobusTest reads the app name, ID, and icon directly from this manifest.
webOS .ipk Must contain a valid appinfo.json describing the app ID, title, and version.

Create your project with Project Type set to Tizen OS or Web OS — see Project Types — then upload your build from the Project Home page as you would for any other platform.

Configuration

The setup follows the same steps as Appium Hub, with platformName set to identify the TV platform.

  1. Point your Appium client at the Hub URL:

    http://192.168.1.1:3142/wd/hub

  2. Set platformName in your desired capabilities:

    {
  "platformName": "tizen"
}

    or

    {
  "platformName": "webos"
}

  3. app — Set to the build URL for your uploaded .wgt/.tpk (Tizen) or .ipk (webOS), the same way you would for any other build. See Appium Hub for the build URL format.

  4. device — Add robustest:deviceID to target a specific Tizen or webOS device. Use the Devices API to look up device IDs, filtering by "os": "tizen" or "os": "webos" in the response.

  5. Reserving a device and robustest:jobIdentifier work the same way as documented in Appium Hub — use them to lock a device to your run and group sessions under a single job.

Full example

{
  "platformName": "tizen",
  "robustest:deviceID": "645a2fcfbaec73a39186b64b",
  "robustest:jobIdentifier": "Tizen_Smoke_Tests_v1.0"
}

Triggering via the Job Payload API

To trigger Tizen/webOS Appium jobs from CI/CD using the Job Payload API, use "type": "Appium(App)" and target your Tizen/webOS devices through a device query — for example, filtering on the os attribute:

{
  "devices": {
    "deviceQueries": [
      {
        "minDeviceCount": 1,
        "maxDeviceCount": 1,
        "conditions": [
          { "attribute": "os", "operator": "=", "value": "tizen" }
        ]
      }
    ]
  }
}