History

Mathieu Lecarme 5a70362b79 Fix: AWS.config is a stub.		2020-03-23 15:48:07 +01:00
..
backend	Fix: AWS.config is a stub.	2020-03-23 15:48:07 +01:00
frontend	fixed size limit on server to include crypto overhead	2019-03-06 10:31:50 -08:00
integration	Strip tracking url parameters	2019-10-15 15:29:48 +02:00
.eslintrc.yml	updated eslint config	2019-08-02 12:03:53 -07:00
readme.md
testServer.js	updated ws dependency and slightly improved client side error handling, hung uploads will error instead of hang forever	2019-08-06 14:47:21 -07:00
wdio.circleci.conf.js	Fix port.	2019-03-12 20:56:31 -04:00
wdio.common.conf.js
wdio.docker.conf.js
wdio.local.conf.js
wdio.remote.config.js
wdio.saucelabs.config.js

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.

Integration

Integration tests include UI tests that run with Selenium.

The preferred way to run these locally is with npm run test-integration which requires docker. To watch the tests connect with VNC. On mac enter vnc://localhost:5900 in Safari and use the password secret to connect. For info on debugging a test see the wdio debug docs.