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

36 lines
1.2 KiB
Plaintext
Raw Normal View History

Use #!/usr/bin/env for bash shebangs. /bin/sh and /usr/bin/env are the only two binaries that NixOS provides at a fixed path (outside a buildFHSUserEnv sandbox). This discussion was split from #11004. Signed-off-by: Anders Kaseorg <andersk@mit.edu>
2018-12-18 02:08:53 +01:00
#!/usr/bin/env bash
Use tools/travis/activate-venv in test suites.
2016-07-18 23:22:10 +02:00
tools: Rename tools/travis directory to tools/ci.
2018-12-10 08:05:16 +01:00
source tools/ci/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
lint: Run mypy as part of main linter. To support this, we add a pass_targets option to the main linter library, because with current mypy, it's generally counterproductive to pass the list of files in (can produce spurious errors; isn't faster).
2018-12-17 05:58:06 +01:00
./tools/lint --backend --no-gitlint --no-mypy # gitlint disabled because flaky
travis: Run test-tools in Travis CI backend suite.
2017-03-10 05:21:03 +01:00
./tools/test-tools
tests: Optimize test-backend performance. This optimizes test-backend by skipping webhook tests when run in default mode. Tweaked by tabbott to extend the documentation and update the CI commands.
2019-01-11 01:26:11 +01:00
./tools/test-backend --coverage --include-webhooks
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
mypy: Switch default to daemon mode. There isn't any real advantage to running the non-daemon mode at this point.
2018-12-17 05:49:33 +01:00
# We run mypy without daemon mode, since that's faster given that
# we're only going to run it once.
./tools/run-mypy --no-daemon
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
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: Move optimize-svg to tools/setup/.
2018-08-10 00:39:15 +02:00
./tools/setup/optimize-svg
ci: Enable test-documentation --skip-external-links in CI. Fixes #10942.
2018-12-05 21:39:15 +01:00
# In CI, we only test links we control in test-documentation to avoid flakes
./tools/test-documentation --skip-external-links
test-help-documentation: Skips checking external links. This option causes test-help-documentation to verify internal links only. This prevents documentation from flaking in CI due to links from external websites having failed in the documentation. Based on conversation: https://chat.zulip.org/#narrow/stream/43-automated-testing/subject/quora.20404/near/674997
2018-12-22 13:02:32 +01:00
./tools/test-help-documentation --skip-external-links
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
tests: Disable test-queue-worker-reload test. This test is low value (it's for testing a very specific feature/bug), is slow, and apparently flakes in CI occasionally.
2018-06-05 18:23:12 +02:00
# This test has been persistently flaky at like 1% frequency, is slow,
# and is for a very specific single feature, so we don't run it by default:
# ./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
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.