zulip/tools/ci/backend
Anders Kaseorg 392175d6e8 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-17 17:21:08 -08:00

36 lines
1.1 KiB
Bash
Executable File

#!/usr/bin/env bash
source tools/ci/activate-venv
echo "Test suite is running under $(python --version)."
set -e
set -x
./tools/lint --backend --no-gitlint --no-mypy # gitlint disabled because flaky
./tools/test-tools
./tools/test-backend --coverage
# We run mypy after the backend tests so we get output from the
# backend tests, which tend to uncover more serious problems, first.
./tools/run-mypy --version
# 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
./tools/test-migrations
./tools/setup/optimize-svg
# In CI, we only test links we control in test-documentation to avoid flakes
./tools/test-documentation --skip-external-links
./tools/test-help-documentation
./tools/test-api
./tools/test-locked-requirements
./tools/test-run-dev
# 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
# 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.