timvisee 94e826e1e2 Fix incorrect development server port in documentation 4 лет назад
..
backend 81e9d81dab implemented download tokens 4 лет назад
frontend 81e9d81dab implemented download tokens 4 лет назад
integration 114068c531 Strip tracking url parameters 5 лет назад
.eslintrc.yml f036df5f47 updated eslint config 5 лет назад
readme.md 94e826e1e2 Fix incorrect development server port in documentation 4 лет назад
testServer.js 527040afef updated ws dependency and slightly improved client side error handling, hung uploads will error instead of hang forever 5 лет назад
wdio.circleci.conf.js 6559afba37 Fix port. 5 лет назад
wdio.common.conf.js 76de2b29a5 cleaned up integration test flow 6 лет назад
wdio.docker.conf.js 1e62aa976d reimplemented l10n using dynamic import() (#1012) 6 лет назад
wdio.local.conf.js 76de2b29a5 cleaned up integration test flow 6 лет назад
wdio.remote.config.js 76de2b29a5 cleaned up integration test flow 6 лет назад
wdio.saucelabs.config.js 76de2b29a5 cleaned up integration test flow 6 лет назад

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:1337/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.