Automated end-to-end acceptance tests for the wp-calypso client and WordPress.com in general.

brew install node-js chromedriver

git submodule init
git submodule update

npm install
npm pack lib/reporter
npm install ./spec-xunit-slack-reporter-0.0.1.tgz

./run.sh -g

./mocha/bin/mocha specs/wp-log-in-out-spec.js lib/after.js

Note: you can also change the spec temporarily the use the .only syntax so it is the only spec that runs (making sure this isn't committed)

eg.

test.describe.only( 'Logging In and Out:', function() {

The run.sh script takes the following parameters, which can be combined to execute a variety of suites

-R		              - Use custom Slack/Spec/XUnit reporter, otherwise just use Spec reporter
-p [jobs]         - Execute [num] jobs in parallel (experimental)
-s		              - Screensizes in a comma-separated list (defaults to mobile,desktop,tablet)
-g		              - Execute general tests in the specs/ directory
-i		              - Execute i18n tests in the specs-i18n/ directory
-v [all/critical] - Execute the visdiff tests in specs-visdiff[/critical].  Must specify either 'all' or 'critical'.
-h		              - This help listing

All tests should be written to work in three modes: desktop (1440 wide), tablet (1024 wide) and mobile (375 wide).

You can run tests in different modes by setting an environment variable BROWSERSIZE to either desktop, tablet or mobile.

Eg:

env BROWSERSIZE=tablet ./node_modules/mocha/bin/mocha --compilers js:babel-register specs lib/after.js

Or you can use the -s option on the run.sh script:

./run.sh -g -s mobile ./run.sh -g -s desktop,tablet

The tests use the node config library to specify config values for the tests.

Under the config directory, there are files for each environment: default.json is the base for all environments, then development.json for local, and test.json for CI.

You can also use local config files that are not committed.

The config files should be added under the config/ tree and should follow the naming scheme: local-<env>.json

The properties in the local configuration override the default.json properties. This is useful for local testing of different configurations on local, e.g. testing on local Calypso instance, instead of live one.

If the configuration doesn't exist, the code falls back to using the environmental variables.

Note: NODE_ENV is still required, as it is used to determine what <env> config to load.

For example: export NODE_ENV='personal'

An example configuration file is provided.

The local configurations are excluded from the repository, in order to prevent accidental commit of sensitive data.

Please don't commit usernames and passwords in these files!

Note: As the NODE_CONFIG variable is growing unwieldy for use in CircleCI, some environment variables are also being split out into separate entries. These are listed below the Config Values section.

A full list of config values are:

These environment variables are intended for use inside CircleCI, to control which tests are being run