SETUP

1. Optionally change POSTGRES_USER, POSTGRES_PASSWORD and POSTGRES_DB in the services section of wercker.yml file

2. Optionally change values for other variables in the ENVIRONMENT file

3. run $ wercker dev --publish 8000 to start container

4. Access http://localhost:8000

Tests

Tests always run when you commit, but you may want to run them mannualy sometimes. Therefore:

• To manually run the tests, do wercker build --direct-mount --pipeline tests
• To manually run static validation (flake8) of the files you have changed, do wercker build --direct-mount --pipeline static-validation

Commiting

Every time you do git commit the script.pre-commit.sh will run. It will trigger, in order:

• static validation of the code, running flake8
• backend tests (django unit tests)
• frontend tests (karma configures tests).

If any of this steps fail, file won't be commited.

(After you run the tests, you can see a coverage report of the backend tests at http://localhost:8000/cover/index.html)

You can read more about these tests in the readme_werker.md on this directory.

Development workflow#

• All features or anything which is not a one liner goes into a branch which results in a PR to staging. Which then must be reviewed, and propgated into a pull request.
• One liners and small patches can go to staging, with a PR to release.
• No commits, nor rebases on release

nexchange