/wdio-service

Webdriver.io service for Waldo

Primary LanguageTypeScriptMIT LicenseMIT

WebdriverIO Waldo Service

CI

A WebdriverIO service that provides better integration with Waldo.

This package provides:

  • Automatic configuration of Waldo as the webdriver endpoint.
  • A collectin of additional commands to ease mobile testing.
  • A TypeScript definition for the options and mobile-specific capabilities.

Installation

The easiest way to install this package is to define @waldoapp/wdio-service as a devDependency in your package.json:

npm install @waldoapp/wdio-service --save-dev

Instructions on how to install WebdriverIO can be found here.

Configuration

To use the Waldo service, you need to provide a valid Waldo API token. This token can be specified by defining the WALDO_API_TOKEN environment variable, or by including the key option in your wdio.conf.ts file.

The API token can be either a user-scoped token for development found in the “Profile” tab of your Waldo account settings, or an application-scoped CI token found in the “General” tab of the “Configuration” for your app.

// wdio.conf.ts
import '@waldoapp/wdio-service';

export const config: WebdriverIO.Config = {
  // This is done automatically if no key is provided,
  // the WALDO_API_TOKEN environment variable is used
  key: process.env.WALDO_API_TOKEN,

  services: [
    [
      '@waldoapp/wdio-service',
      {
        showSession: true,
      },
    ],
  ],
};

In order to run, you must upload your application binary to Waldo. A successful upload generates a build version ID of the form appv-0123456789abcdef. This version ID must then be provided in either the versionId option, or the appium:app capability field for Appium compatibility.

You do not need to provide the versionId if instead you specify an existing running session with the sessionId option.

Waldo service options

To authorize the Waldo service your configuration must contain a key option.

token

The security token.

This can also be specified with either key in the test runner options, or the WALDO_API_TOKEN environment variable.

Type: string
Default: undefined

waldoMode

For compatibility, the default behavior of the Waldo service is to return a tree similar to the one returned by Appium.

This option enables full Waldo tree mode. In this mode the tree returned is typically much better as it unifies native elements, Web views, React Native, and Flutter elements. However, the schema is different and incompatible with scripts that do not specifically target Waldo.

Type: boolean
Default: false

showSession

Opens the Waldo interactive session viewer in a browser when the test is started.

This option has no effect when the sessionId option is specified.

Type: boolean
Default: false

waitSessionReady

Waits for the session to be fully ready, and the application launched, before starting the test. Otherwise, the test starts as soon as the device is available.

Type: boolean
Default: true

sessionId

The ID of an existing Waldo session (created via Sessions > Live > Start session) to connect to. This is useful for interactive development.

The session ID can also be specified with the WALDO_SESSION_ID (or SESSION_ID) environment variable.

Type: string
Default: undefined

versionId

The ID of the app (build) version to use for the test session (for example, appv-0123456789abcdef).

The version ID can also be specified with the WALDO_APP_VERSION_ID (or VERSION_ID) environment variable.

For Appium compatibility, this option can also be specified in the appium:app capability field.

Type: string
Default: undefined

Device capabilities

Most of the service options can also be specified in the capabilities object for a specific device inside the waldo:options key:

capabilities: [
  {
    platformName: 'Android',
    deviceName: 'Pixel 3a',
    'waldo:options': {
      showSession: true,
    },
  },
];

deviceName

The name of the device to use for the test session (for example, iPhone 15 or Pixel 7).

If this option is not specified, the default device configured for the app in Waldo is used.

Type: string
Default: undefined

osVersion

The operating system version to use (for example, 17.0 or 33.0).

If this option is not specified, the default device configured for the app in Waldo is used.

Type: string
Default: undefined