54e78b6274
test_upload: This will create a file and make sure it uploads by verifying a file uploads and is assigned a URL.
test_download: This will create a file, upload it and then download it making sure it is the same filename that was uploaded. We can expand this later to maybe check the sizes and such.
test_progress: This will create a file and make sure the progress bar shows up after it begins uploading.
These are python tests and use Pipenv to manage dependencies as well as tox as the virtualenv manager, and finally pytest as the test runner.
|
||
|---|---|---|
| .. | ||
| backend | ||
| frontend | ||
| integration | ||
| .eslintrc.yml | ||
| readme.md | ||
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.