zulip/tools/test-backend

#!/usr/bin/env bash
set -e

target='zerver'

case "$1" in
    zerver*)
      target="$1"
      shift
      ;;
esac

cd "$(dirname "$0")"/..
./tools/generate-fixtures
# "-u" uses unbuffered IO, which is important when wrapping it in subprocess
export PYTHONUNBUFFERED="y"
/usr/bin/env python2.7 ./manage.py test "$target" --settings=zproject.test_settings "$@"
Add support for running OpenBSD in development environment. 2016-01-12 13:08:43 +01:00			`#!/usr/bin/env bash`
			`set -e`
Add tools/test-backend script to run backend tests. (imported from commit fde4c7deb1e64e8cca9d62cda905f13d90392961) 2013-01-10 19:22:16 +01:00
[manual] Rename Django app from zephyr to zerver. This needs to be deployed to both staging and prod at the same off-peak time (and the schema migration run). At the time it is deployed, we need to make a few changes directly in the database: (1) UPDATE django_content_type set app_label='zerver' where app_label='zephyr'; (2) UPDATE south_migrationhistory set app_name='zerver' where app_name='zephyr'; (imported from commit eb3fd719571740189514ef0b884738cb30df1320) 2013-07-29 23:03:31 +02:00			`target='zerver'`
test-backend: Allow running a subset of tests This now allows e.g. ./tools/test-backend zephyr.BugdownTest or ./tools/test-backend zephyr.BugdownTest --verbosity=2 but unfortunately not ./tools/test-backend --verbosity=2 zephyr.BugdownTest (imported from commit 95302db3efe45182d789c40c2a2899230a06b091) 2013-02-01 21:38:56 +01:00
			`case "$1" in`
[manual] Rename Django app from zephyr to zerver. This needs to be deployed to both staging and prod at the same off-peak time (and the schema migration run). At the time it is deployed, we need to make a few changes directly in the database: (1) UPDATE django_content_type set app_label='zerver' where app_label='zephyr'; (2) UPDATE south_migrationhistory set app_name='zerver' where app_name='zephyr'; (imported from commit eb3fd719571740189514ef0b884738cb30df1320) 2013-07-29 23:03:31 +02:00			`zerver*)`
test-backend: Allow running a subset of tests This now allows e.g. ./tools/test-backend zephyr.BugdownTest or ./tools/test-backend zephyr.BugdownTest --verbosity=2 but unfortunately not ./tools/test-backend --verbosity=2 zephyr.BugdownTest (imported from commit 95302db3efe45182d789c40c2a2899230a06b091) 2013-02-01 21:38:56 +01:00			`target="$1"`
			`shift`
			`;;`
			`esac`

Add tools/test-backend script to run backend tests. (imported from commit fde4c7deb1e64e8cca9d62cda905f13d90392961) 2013-01-10 19:22:16 +01:00			`cd "$(dirname "$0")"/..`
Move generate-fixtures to tools/. (imported from commit 3d452b17e315ba9adf91e33408a7711d16b069a2) 2013-08-07 21:41:34 +02:00			`./tools/generate-fixtures`
We're no longer using the review script. (imported from commit 9840ebdfdacee6e3cb32934b81502c70c133e2b0) 2015-09-20 09:10:54 +02:00			`# "-u" uses unbuffered IO, which is important when wrapping it in subprocess`
Fix buggy #! lines using "/usr/bin/env python2.7 -u". The #! line processing interpreted the argument to pass to `env` as "python2.7 -u", which obviously isn't a real program. We fix this by setting the PYTHONUNBUFFERED environment variable inside the program, which has the same effect. Thanks to Dan Fedele for the bug report and suggested solution! 2015-11-16 17:40:32 +01:00			`export PYTHONUNBUFFERED="y"`
			`/usr/bin/env python2.7 ./manage.py test "$target" --settings=zproject.test_settings "$@"`