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

nemo-drivex

v1.0.0

Published

Selenium webdriver extensions for Nemo automation framework

Downloads

9

Readme

nemo-drivex

Selenium webdriver extensions for Nemo automation framework. Adapts JSON-formatted locator objects to common selenium-webdriver operations.

Unless you plan to get your hands dirty and author your own 'view' plugin (see nemo-view), you probably won't be interacting with nemo-drivex directly, besides adding it as a dependency and adding it to your nemo-plugins.json config. If you are planning to use nemo-view, just start with the docs there.

Register as "drivex" (see below)

Build Status

Installation

  1. Please install nemo to your project as described here: https://github.com/paypal/nemo/blob/master/README.md
  2. Add this plugin to your package.json dev dependencies ("nemo-drivex": "^0.3.0")
  3. npm install
  4. add nemo-drivex to your config/nemo-plugins.json file
{
	"plugins": {
		"drivex": {
			"module": "nemo-drivex",
			"register": true
		}
	}
}

Locator explanation

The JSON locators expected by nemo-drivex would look like this:

{
  "locator": "#result .result",
  "type": "id"
}

type would be any of the accepted locator strategies of the current version of selenium-webdriver: e.g. id, name, css, className, linkText, partialLinkText

locator would be the string which would locate the element(s) via the selected strategy

##Example usage

var resultEl = nemo.drivex.find({'locator': '#result .result', 'type': 'css'});

//resultEl will be a selenium-webdriver promise, which will resolve to a found element or null

Debugging

nemo-drivex uses the debug module. For detailed debug messages, set DEBUG=nemo-drivex to the running process.

API

Array

Promise

Array

Promise

Array

Promise

Array

Promise

LocatorJSON

WebElement

Promise

LocatorJSON

WebElement

Promise

Array

Promise

LocatorJSON

WebElement

Promise

LocatorJSON

Number

Promise

LocatorJSON

Number

Promise

object

string

string