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

33 lines
899 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
travis: Log the Python version. This allows us to ascertain the Python version under which we ran the tests.
2017-09-04 06:15:20 +02:00
echo "Test suite is running under $(python --version)."
Use tools/travis/activate-venv in test suites.
2016-07-18 23:22:10 +02:00
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
quick fix: Turn off git lint for Travis builds. We may be having problems with git lint, so this is a quick fix to hopefully get builds working again.
2017-12-27 21:51:21 +01:00
#./tools/lint --backend ${CIRCLECI:+--no-gitlint}
# TEMP: turn off git lint
./tools/lint --backend --no-gitlint
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: Merge the static-analysis build into backend. [Tweaked by gnprice to leave the use of --linecoverage-report unmodified for now.]
2017-08-27 22:39:58 +02:00
# We run mypy after the backend tests so we get output from the
# backend tests, which tend to uncover more serious problems, first.
run-mypy: Move "which mypy" noise into --version, and use in Travis. Printing the version in Travis builds will help in debugging when we get different results there from locally. The new `--version` path also gives us a handy place to put the "what mypy command are we running" diagnostic, getting it out of the way of normal interactive use.
2017-09-26 23:38:56 +02:00
./tools/run-mypy --version
travis: Merge the static-analysis build into backend. [Tweaked by gnprice to leave the use of --linecoverage-report unmodified for now.]
2017-08-27 22:39:58 +02:00
./tools/run-mypy --linecoverage-report
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
circleci: Skip checking links in documentation for now. This is fairly often -- though not always! -- failing, with a nasty failure mode where it takes like 6 minutes to time out. See discussion on #7748 (search for "bad link"). Actually, after seeing it happen just now when running test-documentation on my laptop, on some other link, it occurs to me that I've seen this before -- it's fairly common in Travis, too. It's just that it doesn't actually cause the build to fail :-/, and on Travis we haven't been paying as close attention to slow builds as we are on Circle right now.
2018-01-09 19:44:21 +01:00
./tools/test-documentation ${CIRCLECI:+--skip-check-links}
tools: Remove `.py` extensions from user scripts.
2017-10-09 12:00:05 +02:00
./tools/test-help-documentation
travis: Run test-api in Travis CI.
2017-01-26 01:42:17 +01:00
./tools/test-api
tools: Rewrite `test-locked-requirements` to be more performant. This commit modifies `test-locked-requirements` to use some caching so that we don't need to use the `update-locked-requirements` tool everytime for checking the validity of locked requirements as it is slow. Fixes: #6969.
2017-10-28 19:12:45 +02:00
./tools/test-locked-requirements
Enable test-run-dev.
2017-12-29 08:48:44 +01:00
./tools/test-run-dev
travis: Enable test-queue-worker-reload. Fixes #1341
2018-01-01 07:52:34 +01:00
./tools/test-queue-worker-reload
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
Slack importer: Add Travis tests.
2017-12-08 11:29:37 +01:00
./tools/test-slack-importer
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.