zulip/tools/test-backend

#!/bin/bash -e

target='zerver'

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

cd "$(dirname "$0")"/..
./zerver/tests/generate-fixtures
# "-u" uses unbuffered IO, which is important when wrapping it in
# something like subprocess (as tools/review does)
/usr/bin/env python -u ./manage.py test "$target" --settings=humbug.test_settings "$@"
Add tools/test-backend script to run backend tests. (imported from commit fde4c7deb1e64e8cca9d62cda905f13d90392961) 2013-01-10 19:22:16 +01:00			`#!/bin/bash -e`

[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")"/..`
[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/tests/generate-fixtures`
[manual] Modify review to allow testing+review in the background Does a test-all using /tmp. Not safe to run with other tests simultaneously. You use it just like tools/review, and on a successful test-all it will submit the code review, without tying up your git working directory. It depends on new patches to the acrefoot-bulk_create_with_id-1.5.1 branch of django. Updating this is the [manual] step required. Since test-all doesn't happen on staging or prod, this is not required for this commit to be deployed, but other django patches will help with the SSL connection errors we've been seeing. (imported from commit 3fd3ff00240a2d648c4c54748a8a70616067ef7d) 2013-05-30 22:17:01 +02:00			`# "-u" uses unbuffered IO, which is important when wrapping it in`
			`# something like subprocess (as tools/review does)`
			`/usr/bin/env python -u ./manage.py test "$target" --settings=humbug.test_settings "$@"`