![Introducing Enhanced Alert Actions and Triage Functionality](https://cdn.sanity.io/images/cgdhsj6q/production/fe71306d515f85de6139b46745ea7180362324f0-2530x946.png?w=800&fit=max&auto=format)
Product
Introducing Enhanced Alert Actions and Triage Functionality
Socket now supports four distinct alert actions instead of the previous two, and alert triaging allows users to override the actions taken for all individual alerts.
nemo-locatex
Advanced tools
Readme
Specify different Nemo locator objects per-locale.
{
"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.
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.
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"
}
]
},
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.
FAQs
Add Locale behavior to Nemo locators
The npm package nemo-locatex receives a total of 1 weekly downloads. As such, nemo-locatex popularity was classified as not popular.
We found that nemo-locatex demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Product
Socket now supports four distinct alert actions instead of the previous two, and alert triaging allows users to override the actions taken for all individual alerts.
Security News
Polyfill.io has been serving malware for months via its CDN, after the project's open source maintainer sold the service to a company based in China.
Security News
OpenSSF is warning open source maintainers to stay vigilant against reputation farming on GitHub, where users artificially inflate their status by manipulating interactions on closed issues and PRs.