Name: rowdy
Owner: Formidable
Description: A small, rambunctious WD.js / WebdriverIO configuration wrapper.
Created: 2014-09-24 00:58:47.0
Updated: 2018-01-16 23:49:55.0
Pushed: 2016-03-19 21:28:00.0
Size: 225
Language: JavaScript
GitHub Committers
| User | Most Recent Commit | # Commits |
|---|
Other Committers
| User | Most Recent Commit | # Commits |
|---|
A small, rambunctious configuration wrapper for WD.js or WebdriverIO
Main features:
First, install the library.
m install --save-dev rowdy
If you want to have Rowdy run and control a local Selenium server, then install the standalone client and run the install scripts:
m install --save-dev selenium-standalone
m run install-selenium
This shells out to selenium-standalone and is necessary at some point in your
integration if using the standalone (local) server.
The above steps are necessary if the configuration value
settings.local.server.start is true. You can skip the steps if you are
separately running / managing a local Selenium server or using a remote Selenium
farm (e.g., Sauce Labs or BrowserStack).
Then, install the necessary client libraries.
m install --save-dev wd
m install --save-dev webdriverio saucelabs
Note: If using SauceLabs + WebdriverIO, we lazy require the Sauce Labs
module to upload results of “done” to your SL account.
Note: Rowdy requires webdriverio at version v3.0.0 or above.
If you intend to use Sauce Labs + guacamole-provide environments, then:
m install --save-dev guacamole
By default Rowdy will lazy initialize the library's included
config.js configuration file. (The first access of most
rowdy.* properties / methods will force this.)
However, on first import of Rowdy, you can override this behavior to do things like override parts of the default configuration:
tart with default configuration.
config = require("rowdy/config");
ig.server.logger = true;
.. any other mutations
ass configuration in.
rowdy = require("rowdy")(config);
Or, you can simply copy config.js to your project, edit it as appropriate and load:
config = require("./PATH/TO/config");
rowdy = require("rowdy")(config);
Start the local Selenium server on a different port:
WDY_OPTIONS='{ "server": { "port":4321 } }' \
m run test
Have client hit an already running local Selenium server without starting its own:
one terminal
ava -jar node_modules/selenium-standalone/.selenium/selenium-server/2.45.0-server.jar \
port 4321 \
Dphantomjs.binary.path=node_modules/phantomjs/lib/phantom/bin/phantomjs
another...
WDY_OPTIONS='{ "client": { "port":4321 }, "server": { "start":false } }' \
m run test
We use guacamole to have
automatic access to all of the test environments Sauce Labs supports
(e.g., firefox_38_Windows_2012_R2_Desktop, safari_7_OS_X_10_9_Desktop).
If you npm install guacamole, then by default Rowdy will use and enable
those environments for use in configuration. Once installed, you can view
all of the available environments with:
ew environments
de_modules/.bin/guacamole
nerate a cached shrinkwrap file
de_modules/.bin/guacamole --generate-shrinkwrap
Rowdy uses a cached version of Sauce Labs configurations in the
guacamole-shrinkwrap.json file so that
guacamole doesn't query the Sauce Labs API at runtime.
Disabling Guacamole: If you don't want to use the guacamole environments
with Sauce Labs, then you can skip the npm install and just make sure the
following is active in your Rowdy configuration:
tions: {
guacamole: {
enabled: false
}
(By default guacamole.enabled is true if npm installed and false otherwise,
so if you use the default Rowdy configuration, no code changes are needed.)
And then you should add your own bespoke Sauce Labs settings in configuration at:
ttings: {
sauceLabs: {
"mac-safari-7": { /* Sauce Labs capabilities */ }
}
One of the Rowdy peer dependencies is selenium-standalone. This package
contains an install script that you may need (and do need on Windows):
de_modules/.bin/selenium-standalone install
Some other tips and tricks:
Recent Safari updates have broken automatic driver usage, so you need a series of tedious steps per http://elementalselenium.com/tips/69-safari:
https://github.com/SeleniumHQ/selenium/raw/selenium-VERSION/javascript/safari-driver/prebuilt/SafariDriver.safariextz. A current version used in selenium-standalone is 2.45.0, so
that would correspond to:
github.com/SeleniumHQ/selenium/raw/selenium-2.45.0/javascript/safari-driver/prebuilt/SafariDriver.safariextzSee https://code.google.com/p/selenium/wiki/InternetExplorerDriver#Required_Configuration for extra steps needed to work with local IE. Anecdotally, for Win7+IE11 in a VM, the only actually tweak needed was:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BFCACHE
and add DWORD of iexplore.exe defaulted to 0 value.TODO: API is still settling out.
We provide full working examples of the Mocha Adapter:
TODO: Add a full guide for configuring the adapter and (1) the options,
(2) adapter.refreshClient() use, (3) adapter.client use.
The full API to WD.js is available at: https://github.com/admc/wd/blob/master/doc/api.md
WebdriverIO provides the following useful documentation:
Please see the Contributions Guide for how to help out with the plugin.
We test all changes with Travis CI. Here's our current build status:
We also do multi-browser testing thanks to donated VM time from Sauce Labs and BrowserStack. Here's our Sauce Labs build matrix:
