enable cucumber tests on selenium and sauce labs
Add instructions for running Selenium tests locally.
Run sauce tests against capybara server

@maxfliri
set sensible name for sauce jobs
run scenarios as separate sauce jobs
avoid race conditions, allow app_host option, change default sauce browsers
run scenarios specific to browser features
Allow Sauce tests to be run with alternative asset host

Allows us to run tests without explicitly starting up static.
Expand README around running tests.
Integrate sauce labs with travis

See: https://saucelabs.com/opensource/travis
Merge branch 'master' into automated-browser-testing

Conflicts:
	features/overview.feature
	features/step_definitions/common_steps.rb
Fix path for services list in browser tests.
Remove redundant feature tests.
Run a smaller set of features through sauce

Sauce tests take a long time and are currently failing when run through
travis.
Debug why sauce connect is not working in travis

From the sauce website it looks like sauce connect isn't running. This
change should give us a bit more information.
Regenerate secrets after debugging

Key was reporting in the debugging output.
Reset the sauce key again and remove the ps check
Try using Travis addons

http://about.travis-ci.org/blog/2013-05-03-introducing-addons/
Revert "Try using Travis addons"

This reverts commit ef25bcb3dd1fbb2336e98cfde2473aa242a68693.

Credentials are already in place, but I didn't understand it.
Specific versions in Gemfile

sauce and parallel_tests