Roku Driver is a WebDriver that allows testing channels/screensavers using any webdriver client.

• Appium 2
• Roku Device with fresh OS and mentioned below settings:
  • Roku OS 9.4 or Newest
  • Enable Developer Settings
  • Disable Screensaver (optional)

appium driver install --source npm @dlenroc/appium-roku-driver

Thanks to the Appium and WebDriver protocol, this driver works just like other web drivers, but there are a couple of things worth mentioning.

Like other drivers, roku-driver by default uses the so-called fast reset algorithm, in which registries are cleared before each test, and a full reinstallation occurs only if the channel differs from the one already installed.

The following location strategies are supported: tag name, link text, partial link text, css selector and xpath.

• ECP (default) External Control Protocol is a context that finds elements quickly, but does not see many attributes.

• ODC (WIP) On Device Component is a context that finds elements slower, but see all attributes. (can be tunned using elementResponseAttributes setting).

• input - Sends a custom event to the launched channel.

  driver.url('roku://input?<key>=<value>');

• launch - Launches given channel with specific arguments.

  driver.url('roku://launch/:channel_id?<key>=<value>');

In roku appId is always dev for sideloaded channel or a number for channels installed from store (ex: 12 for Netflix).

driver.queryAppState('dev');
driver.queryAppState('12');

Note: most commands only work with SceneGrapth based sideloaded channels.

Given driver allows testing of Screensavers via appium:entryPoint capability.

• channel (default) - Opens channel itself.
• screensaver - Opens your channel screen saver.
• screensaver-settings - Opens your channel screen saver settings.

Note: Usually screensavers open on their own and close immediately after any user input is sent, but when entryPoint screensaver is used, it runs in the context of the channel, so the input interaction does not close it (BACK and HOME buttons are an exception).

In Roku world:

• Registries are used to store persistent information such as sessions and settings.
• Input / Launch parameters are used for deep linking and/or controlling app behavior.

So, knowing this, we can significantly speed up the automation by skipping authorization/configuration steps.

Note: appium:arguments and appium:registry will contain different values in your case.

const capabilities = {
  ...commonCapabilities,

  // Launch parameters
  'appium:arguments': {
    contentId: 1234,
    mediaType: 'movie',
  },

  // Registry sections Settings
  'appium:registry': {
    account: {
      token: '<user_token>',
    },
  },
};

The following action types are supported:

• keyDown, keyUp - presses/releases given key.
• pointerMove - focuses the element using arrow buttons.
• pause - waits given amounts of milliseconds.

Below are the key codes and their equivalents in the roku remote.

If adding a vendor prefix is a problem, @appium/relaxed-caps-plugin can be used to get rid of them.

The supported commands are listed in the sections below but note that they may have a different name in the client you are using

Example: calling the setContext command

// Java
driver.context('ECP');

// WebdriverIO
driver.switchContext('ECP');

In addition to the standard apium commands, Roku has several additional features that go beyond the appium protocol, so they are available through a javascript executor and a script in the following format <component>:<command>

The following components are available: ecp, debugServer, developerServer, and odc

Example:

// with args
driver.execute('ecp:launch', [{ appId: 'dev', params: {} }]);

// without args
const playerState = driver.execute('ecp:queryMediaPlayer');
playerState.duration;