Add e2e tests (Protractor)

[paulbert]

This commit adds end to end tests with Protractor for the app with a simple login test to get started.

Tests run on a headless instance of Chrome. To do this, I added a Chrome installation to the Vagrantfile.

Since the tests are running within Vagrant, they also access the CouchDB on port 5984 rather than 2200 as they do in the app. I added an Angular environment file for tests which will swap in that port number, so the tests need to be run with the command npm e2e --environment test.

Currently the tests setup by creating a test user (username is available to tests in the browser.params.user variable and password is always e2e) and teardown by deleting that user. As we secure the app with admin users, this will need to change. Not sure what the ideal solution is for this, but having separate test DBs which cannot replicate to our production instances is my first thought.

Full commands to run the tests:

vagrant ssh
cd /vagrant
ng e2e --environment test

[empeje]

Should we change the travis to run headless e2e test too? @dogi @daisywatson @paulbert ?

[dogi]

Jasmine started

  Login
    ✓ should display page header
    ✓ should login

Executed 2 of 2 specs SUCCESS in 12 secs.
Completed tests and removed new user: e2e_1506525200021
[15:13:47] I/launcher - 0 instance(s) of WebDriver still running
[15:13:47] I/launcher - chrome #01 passed