Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/tools/travis/backend

26 lines
744 B
Plaintext
Raw Normal View History

Expand testing done via Travis CI to cover production pipeline. With this change, we are now testing the production static asset pipeline and installation process in a new testing job (and also run the frontend/backend tests separately). This means that changes that break the Zulip static asset pipeline or production installation process are more likely to fail tests. The testing is imperfect in that it does not have proper isolation -- we build a complete Zulip development environment and then install a Zulip production environment on top of it, so e.g. any apt dependencies installed for Zulip development will still be available for the Zulip production environment. But, it's better than nothing! A good v2 of this would be to have the production setup process just install the minimum stuff needed to run `build-release-tarball` and then uninstall it / clean it up so that we can do a more clear production installation, but that's more work.
2015-10-15 01:47:42 +02:00
#!/bin/bash
Use tools/travis/activate-venv in test suites.
2016-07-18 23:22:10 +02:00
source tools/travis/activate-venv
Expand testing done via Travis CI to cover production pipeline. With this change, we are now testing the production static asset pipeline and installation process in a new testing job (and also run the frontend/backend tests separately). This means that changes that break the Zulip static asset pipeline or production installation process are more likely to fail tests. The testing is imperfect in that it does not have proper isolation -- we build a complete Zulip development environment and then install a Zulip production environment on top of it, so e.g. any apt dependencies installed for Zulip development will still be available for the Zulip production environment. But, it's better than nothing! A good v2 of this would be to have the production setup process just install the minimum stuff needed to run `build-release-tarball` and then uninstall it / clean it up so that we can do a more clear production installation, but that's more work.
2015-10-15 01:47:42 +02:00
set -e
set -x
Use tools/travis/activate-venv in test suites.
2016-07-18 23:22:10 +02:00
Rename tools/lint-all to tools/lint. Fixes #4574.
2017-04-21 23:07:06 +02:00
./tools/lint --pep8 # Include the slow and thus non-default pep8 linter check
tests: Bring all the top-level test scripts into alignment on what to test. Notably, this adds our checks on translated message strings to `tools/test-all`, so that they don't cause surprise failures in CI after a branch is pushed. (Alternately they could have gone in `tools/lint` to accomplish the same goal, but `makemessages` which they depend on is quite slow -- on my machine it takes 7s, compared to 10s for all of `tools/lint`.)
2017-07-25 04:46:15 +02:00
python manage.py makemessages --locale en
python -W ignore tools/check-capitalization --no-generate
python -W ignore tools/check-frontend-i18n --no-generate
travis: Run test-tools in Travis CI backend suite.
2017-03-10 05:21:03 +01:00
./tools/test-tools
test-backend: Disable verbose coverage display.
2017-03-05 07:41:54 +01:00
./tools/test-backend --coverage
travis: Test whether migrations are consistent with models. This should automatically catch mistakes where someone updates the database models but forgets to generate migrations afterwards.
2016-01-10 05:15:19 +01:00
./tools/test-migrations
tools: Add optimize-svg tool for checking for unoptimized SVG files.
2017-05-23 00:11:08 +02:00
./tools/optimize-svg
docs-test: Check only http 404 error for external links. - Raise exception only for http 404 error rensponse, for other http error codes used logging to notify devs about wrong links.
2016-10-29 19:54:17 +02:00
./tools/test-documentation
travis: Add test-help-documentation to CI for real. 75c4e3191d17bf22dddfc3b7711c6395587dd82d actually only added it to `test-all`.
2016-12-27 01:17:25 +01:00
./tools/test-help-documentation.py
travis: Run test-api in Travis CI.
2017-01-26 01:42:17 +01:00
./tools/test-api
tests: Bring all the top-level test scripts into alignment on what to test. Notably, this adds our checks on translated message strings to `tools/test-all`, so that they don't cause surprise failures in CI after a branch is pushed. (Alternately they could have gone in `tools/lint` to accomplish the same goal, but `makemessages` which they depend on is quite slow -- on my machine it takes 7s, compared to 10s for all of `tools/lint`.)
2017-07-25 04:46:15 +02:00
#./tools/test-run-dev # Disabled in CI because flaky.
#./tools/test-queue-worker-reload # Disabled in CI because flaky.
tests: Reorder tests in top-level test scripts to agree with each other. This will make it easier to get the scripts to contain the same set of tests (with explicit, conscious exceptions), and to keep it that way.
2017-07-25 04:37:23 +02:00
tests: Bring all the top-level test scripts into alignment on what to test. Notably, this adds our checks on translated message strings to `tools/test-all`, so that they don't cause surprise failures in CI after a branch is pushed. (Alternately they could have gone in `tools/lint` to accomplish the same goal, but `makemessages` which they depend on is quite slow -- on my machine it takes 7s, compared to 10s for all of `tools/lint`.)
2017-07-25 04:46:15 +02:00
# NB: Everything here should be in `tools/test-all`. If there's a
# reason not to run it there, it should be there as a comment
# explaining why.