npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

appium-android-driver-sunyibin

v2.10.40

Published

Android UiAutomator and Chrome support for Appium

Downloads

5

Readme

NPM version Downloads Dependency Status devDependency Status

Build Status Coverage Status

Appium Android Driver

Appium Android Driver is a test automation tool for Android devices. Appium Android Driver automates native, hybrid and mobile web apps, tested on simulators, emulators and real devices. Appium Android Driver is part of the Appium mobile test automation tool.

Installation

npm install appium-android-driver

Usage

Import Android Driver, set desired capabilities and create a session:

import { AndroidDriver } from `appium-android-driver`

let defaultCaps = {
  app: 'path/to/your.apk',
  deviceName: 'Android',
  platformName: 'Android'
};

let driver = new AndroidDriver();
await driver.createSession(defaultCaps);

Run commands:

await driver.setOrientation('LANDSCAPE');
console.log(await driver.getOrientation()); // -> 'LANDSCAPE'

Specifying and selecting devices/emulators

The driver will attempt to connect to a device/emulator based on these properties in the desiredCapabilities object:

  1. avd: Launch or connect to the emulator with the given name.
  2. udid: Connect to the device with the given UDID.
  3. platformVersion: Connect to the first device or active emulator whose OS begins with the desired OS. This means platformVersion: 5 will take the first 5x device from the output of adb devices if there are multiple available.

If none of these capabilities are given, the driver will connect to the first device or active emulator returned from the output of adb devices.

If more than one of these capabilities are given, the driver will only use first the capability in the order above. That is, avd takes priority over udid, which takes priority over platformVersion.

Commands

| Command | |----------------------------| | activateIMEEngine | | availableIMEEngines | | back | | background | | clear | | click | | complexTap | | deactivateIMEEngine | | defaultContextName | | defaultWebviewName | | doKey | | doTouchAction | | doTouchDrag | | drag | | elementDisplayed | | elementEnabled | | elementSelected | | fakeFlick | | fakeFlickElement | | findElOrEls | | fixRelease | | flick | | getActiveIMEEngine | | getAlertText | | getAttribute | | getContexts | | getCurrentActivity | | getCurrentContext | | getDeviceTime | | getDisplayDensity | | getLocationInView | | getLog | | getLogTypes | | getName | | getNetworkConnection | | getOrientation | | getPageSource | | getScreenshot | | getSize | | getStrings | | getSystemBars | | getText | | getWindowSize | | hideKeyboard | | installApp | | isAppInstalled | | isIMEActivated | | isKeyboardShown | | isLocked | | isWebContext | | keyevent | | keys | | lock | | longPressKeyCode | | onChromedriverStop | | openNotifications | | openSettingsActivity | | parseTouch | | performGesture | | performMultiAction | | performTouch | | pinchClose | | pinchOpen | | postAcceptAlert | | postDismissAlert | | pressKeyCode | | pullFile | | pullFolder | | pushFile | | removeApp | | replaceValue | | reset | | setAlertText | | setContext | | setGeoLocation | | setLocation | | setNetworkConnection | | setOrientation | | setValue | | setUrl | | startActivity | | startChromedriverProxy | | stopChromedriverProxies | | suspendChromedriverProxy | | swipe | | tap | | toggleData | | toggleFlightMode | | toggleLocationServices | | toggleSetting | | toggleWiFi | | touchDown | | touchLongClick | | touchMove | | touchUp | | unlock | | wrapBootstrapDisconnect |

API Notes

lock behaves differently in Android than it does in iOS. In Android it does not take any arguments, and locks the screen and returns immediately.

Watch

npm run watch

Test

npm test