browser-tests

CI and adhoc testing for cross browser API support using nightwatch, selenium and saucelabs

Cross-browser testing using Buildkite CI

After each push Buildkite runs cross-browser UI tests over core libraries and plugins

Running Ad hoc chrome and firefox tests locally

In Chrome yarn test-chrome In Firefox yarn test-firefox

Running cross-browser tests locally

You can run cross-browser tests locally leveraging docker and Sauce Labs by running the following:

docker-compose run
SAUCE_USERNAME=... SAUCE_ACCESS_KEY=... docker-compose run browser-tests .buildkite/run-all-tests.sh

Running Ad hoc cross-browser tests remotely

(For convenience you should add SAUCE_USERNAME and SAUCE_ACCESS_KEY as environment variables)

1. Start the app server
   yarn dev
2. Start sauce connect
   sc -u <saucelabs username> -k <saucelabs access key>
3. Run the tests remotely
   run specific test: yarn test-remote -- --env ie-11
   run all tests: yarn test-remote

The Tests

Basic UI Test

Runs simple UI over core fusion libraries and plugins. In theory should be sufficient to verify necessary API/polyfill support, though we should add more UI interactions to improve confidence level.

Polyfills Test

Off by default. Tests for a selection of ES2015+ utils which are not transpiled by Babel at buildtime. Tested utils are somewhat arbitary as not all are necessarily required by fusion, so only uncomment if you want to test for specific API/polyfill support.

Nightwatch Configuration files

• Buildkite: nightwatch-ci.js
• Ad Hoc (local): nightwatch.js
• Ad Hoc (remote): nightwatch-remote.js

Test folder / file
src_folders: ['src/test/browser/index.js'],

Test environments
e.g.

'chrome-mac': {
  desiredCapabilities: {
    browserName: 'chrome',
    platform: 'macOS 10.12',
  },
},

To add additional test environments see https://wiki.saucelabs.com/display/DOCS/Platform+Configurator#/