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-locatex

v1.0.1

Published

Add Locale behavior to Nemo locators

Downloads

25

Readme

nemo-locatex

Specify different Nemo locator objects per-locale.

Register as "locatex" (see below)

Build Status

Installation

  • Add nemo-locatex to your package.json (see nemo-locatex package.json for version)
  • Add nemo-locatex to your plugins config
{
	"plugins": {
		"drivex": {
			"module": "nemo-drivex",
			"register": true
		},
		"locatex": {
			"module": "nemo-locatex",
			"register": true
		}
	}
}

Now the locatex function will be available in any of your nemo tests which include locators.

Changing your locator files

You don"t need to change your locator files unless you plan to use locale-specific locators. But if you do plan to use them, you need to add locale-specific and default sections to each locator which requires it:

myView.json:

{
	"emailTextInput": {
		"locator": "login_email",
		"type": "id"
	},
	"passwordTextInput": {
		"locator": "login_password",
		"type": "id"
	},
	"loginButton": {
		"default": {
			"locator": "default-login-button",
			"type": "id"
		},
		"DE": {
			"locator": "Das login-button",
			"type": "id"
		}
	},
	"submitButton": {
		"default": {
			"locator": "submit",
			"type": "name"
		} ,
		"FR": {
			"locator": "le submit",
			"type": "name"
		}
	},
	"logoutLink": {
		"locator": "a[href*='cgi-bin/webscr?cmd=_logout']",
		"type": "css"
	}
}

In the above example, two locators are set up to be locale-specific. Three others don't have locale information.

Setting locale

Add locale as a pass-through variable to Nemo in your tests. If you are using grunt, this means add locale to your gruntfile config for your tests as follows:

"options": {
	"mocha": {
		"reportLocation": grunt.option("reportLocation") || "<%=loopmocha.basedir%>/report",
		"timeout": grunt.option("timeout") || 120000,
		"grep": grunt.option("grep") || 0,
		"debug": grunt.option("debug") || 0,
		"reporter": grunt.option("reporter") || "spec"
	},
	"nemoData": {
		"locale": nconf.get("LOCALE") || "default",
		"autoBaseDir": "<%=loopmocha.basedir%>",
		"targetBrowser": nconf.get("TARGET_BROWSER") || "firefox",
		"targetServer": nconf.get("TARGET_SERVER") || "localhost",
		"targetBaseUrl": "http://localhost:8000",
		"seleniumJar": nconf.get("SELENIUM_JAR") || "/usr/local/bin/selenium-standalone.jar",
		"serverProps": {"port": 4444}
	},
	"iterations": [
		{
			"description": "default"
		}
	]
},

Usage in your tests

With LOCALE set in your Nemo grunt config, locatex auto-registered, and with a locator named "myView" pulled in via your nemo.setup:

Where you would have previously had this code:

drivex.find(loc.login.loginButton).click();

Now you would have this instead:

drivex.find(locatex("login.loginButton")).click();

This will use the appropriate locator based on the LOCALE setting.