History

Danny Coates 1a7510070e fixed footer integration test		2018-11-02 11:57:50 -07:00
..
backend	made download count and expiry options server configurable	2018-09-24 15:08:39 -07:00
frontend	reduce log noise in puppeteer test	2018-10-05 09:52:00 -07:00
integration	fixed footer integration test	2018-11-02 11:57:50 -07:00
.eslintrc.yml	Ignore console statements in test/ directory because yolo	2017-07-23 00:06:24 -07:00
readme.md	updated docs	2018-03-07 15:01:08 -08:00
testServer.js	Added webdriverio integration tests	2018-10-03 11:22:30 -07:00
wdio.circleci.conf.js	cleaned up integration test flow	2018-10-04 15:06:39 -07:00
wdio.common.conf.js	cleaned up integration test flow	2018-10-04 15:06:39 -07:00
wdio.docker.conf.js	cleaned up integration test flow	2018-10-04 15:06:39 -07:00
wdio.local.conf.js	cleaned up integration test flow	2018-10-04 15:06:39 -07:00
wdio.remote.config.js	cleaned up integration test flow	2018-10-04 15:06:39 -07:00
wdio.saucelabs.config.js	cleaned up integration test flow	2018-10-04 15:06:39 -07:00

readme.md

Tests

To run all the tests use npm test. This will run the tests and produce a code coverage report at coverage/index.html. The full test suite is run as a hook on each git push. Mocha is our preferred test runner.

Frontend

Unit tests reside in test/frontend/tests.

Frontend tests can be ran in the browser by running npm start and then browsing to http://localhost:8080/test. Doing it this way will watch for changes and rerun the suite automatically.

You can also run them in headless Chrome by using npm run test:frontend. The results will be printed to the console.

Backend

Unit tests reside in test/backend

Backend test can be run with npm run test:backend. Sinon and proxyquire are used for mocking.