Sample report from an integration test:
https://saucelabs.com/beta/tests/7e6958fd51d44abfbb7a5e7a1efe132a/commands
See, e.g., screencast that you can play or see history.

This is to prevent flakyness in our travis infrastructure.

BREAKING CHANGE: Now node 4 is required to build the project. This is
because protractor 3 requires is. I decided to make the switch now,
because it would happen anyway at some point.

With this change I've gone through all ESLint rules at:
http://eslint.org/docs/rules/ and added all of them that I feel make
sense to the project.

This will allow us to focus on business logic of our code, rather than
on style discussions, which are now better guarded thanks to ESLint and
clang-format.

On the final note: it does not matter what concrete lint rules are
enforced (e.g., semicolons or nor). The important part is that they are
enforced by a tool and we do not spend time dicussing about them.

Addresses: #66

This change reformats all files according to clang-format rules (the
same that Angular JS has) and forces the files to comply with the
formatting.

This change makes it possible to run tests, integration tests and lint
on Travis CI. It also prepares a special Gulp task to perform the same
activities locally. This is handy when, e.g., sending a pull requrest.

Next change will actually implement some tests for the backend.

This is to have unified codebase from the beginning of the project.

Added a few simple rules to the linter and fixed all errors through the
codebase. This will allow to wire it up to some automatic checks.

With this file we can run frontend tests with everything wired up for
development. Subsequent pull requests will use this in Gulp file to
facilitate testing.