What is appium-remote-debugger?
The appium-remote-debugger npm package is a tool used for remote debugging of iOS applications. It allows you to interact with and control iOS webviews and Safari instances from a remote environment, which is particularly useful for automated testing scenarios.
What are appium-remote-debugger's main functionalities?
Connecting to a Remote Debugger
This feature allows you to establish a connection to a remote debugger instance. The code sample demonstrates how to create a new RemoteDebugger instance and connect to it using specific parameters like bundleId and platformVersion.
const RemoteDebugger = require('appium-remote-debugger');
const rd = new RemoteDebugger({
bundleId: 'com.apple.mobilesafari',
platformVersion: '14.4',
isSafari: true
});
await rd.connect();
Listing Available Contexts
This feature allows you to list all available contexts (webviews) for a given application. The code sample shows how to select an app and retrieve its contexts.
const contexts = await rd.selectApp('com.apple.mobilesafari');
console.log(contexts);
Executing JavaScript in a Webview
This feature allows you to execute JavaScript code within a webview context. The code sample demonstrates how to execute a simple JavaScript command to get the document title.
const result = await rd.execute('document.title');
console.log(result);
Other packages similar to appium-remote-debugger
webdriverio
WebdriverIO is a popular testing utility for browser and mobile automation. It provides a high-level API to control browsers and mobile applications, similar to appium-remote-debugger, but it supports a wider range of platforms and browsers.
selenium-webdriver
Selenium WebDriver is a widely-used tool for browser automation. It allows you to control web browsers programmatically. While it doesn't specialize in mobile webviews like appium-remote-debugger, it is a robust solution for web automation.
puppeteer
Puppeteer is a Node library which provides a high-level API to control Chrome or Chromium over the DevTools Protocol. It is primarily used for browser automation and offers functionalities similar to appium-remote-debugger but is limited to Chrome/Chromium.
appium-remote-debugger
A Node.js frontend for the Remote Debugger protocol used by Appium to connect to iOS webviews and Safari. Written using ES6+.
Safari's version of the WebKit API
Safari implements a wonky version of the WebKit API. It is not documented. The
JSON version of the protocol is documented in the WebKit source code, in
Source/JavaScriptCore/inspector/protocol/.
There is good documentation for the closely related API from Chrome DevTools, to
be found here.
API
This is an event emitter, which emits a RemoteDebugger.EVENT_PAGE_CHANGE
event when there has been a change to the page. This should be caught and handled as the calling code wishes. It also emits a RemoteDebugger.EVENT_DISCONNECT
event when the server disconnects the last application connected.
The steps to using the RemoteDebugger
involve instantiating an object, then running connect
and selectApp
. After this the instance will be listening for events from the server (i.e., the webview or browser).
Selenium "atoms"
The remote debugger uses the standard Selenium Atoms
to interact with web pages. These need to be manually updated when necessary. To
do so, simply update the branch in the scripts/common.js
, by modifying the SELENIUM_BRANCH
constant at the top of the file. Then run npm run build:atoms
, test and create
a pull request with the resulting changed atoms directory.
Note that to build the atoms it is required that you have the bazel
tool installed. Selenium will
also require that it be installed at a particular version relative to the version of Selenium that
has been checked out by our build script. It is most convenient simply to install
bazelisk
and have it available on your PATH.
One caveat is that there are some changes that are needed for Appium, that are
not yet in the Selenium codebase. See the atoms notes for
details.
Test
npm test
npm e2e-test