Ease execution of tests using Docker => simpler setup instructions in readme

[adrienjoly]

When running:

$ docker-compose up
$ docker-compose exec web npm test

Unit tests are running fine, but getting error mongo: not found when test-reset npm script tries to re-init the testing database.

[adrienjoly]

Hypothesis:

This is caused by the fact that mongodb is reachable only by the mongo service, not the web service on which the npm test command is executed.

[adrienjoly]

=> Trying to add the following lines in Dockerfile:

RUN sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv 7F0CEB10
RUN sudo apt-get install -y mongodb-org-shell
RUN sudo apt-get install -y mongodb-org-tools

(as recommended there: http://corpus.hubwiz.com/2/node.js/27050643.html)

[adrienjoly]

...then:

$ docker-compose build

(as recommended there: docker/compose#1487 (comment))

=> getting sudo: not found

=> trying without sudo

[adrienjoly]

getting Unable to locate package mongodb-org-shell

=> replacing new lines in Dockerfile by:

RUN apt-get update
RUN apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv 7F0CEB10
RUN apt-get install -y mongodb

(as recommended there: https://stackoverflow.com/a/28966356/592254 and https://hub.docker.com/r/richardxxx0x/docker-leanote/builds/bh3enhrdrfscxzrgxxybqol/)

=> now getting couldn't connect to server 127.0.0.1:27017:

> mongo openwhyd_test --eval "db.dropDatabase();" && mongo openwhyd_test ../whydDB/initdb.js && mongo openwhyd_test ../whydDB/initdb_team.js

MongoDB shell version: 2.4.10
connecting to: openwhyd_test
Thu Jul 13 09:04:10.052 Error: couldn't connect to server 127.0.0.1:27017 at src/mongo/shell/mongo.js:145
exception: connect failed

=> Considering another alternative: run mongodb init scripts from the app server instead.

[adrienjoly]

(WIP) currently experimenting with:

• running db init scripts from web server (app.js) --> 4e7674c
• clearing the database and starting/stoping web server from the acceptance test script

current problem: it seems complicated to mix webdriver-based code (synchronous) and callback-based code with console.logs. => my tests start running before I'm done with my before() checks and db inits...

EDIT: it would probably make more sense to execute just unit tests in the container, while providing an easy way to run acceptance/end-to-end tests from outside the container (but connecting to the app server running inside the container)

[adrienjoly]

Different approach was chosen: run tests outside of Docker container,
but enable DB to be also updated from the outside, in order for test scripts to reset the database (#81)