zulip/tools/test-backend

#!/bin/bash -e

target='zephyr'

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

cd "$(dirname "$0")"/..
./zephyr/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`

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='zephyr'`

			`case "$1" in`
			`zephyr*)`
			`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] Humbug testing databases now backed by postgres Currently our test database is backed by sqlite; this commit moves us to using postgres for our all database needs. This, in conjunction with the patched django on github, allow us to have fewer hacks and more true-to-life tests. It also sets the stage for testing the bulk_create and schema search_path patches made to django. Developers will need to run: ./tools/postgres-init-test-db ./tools/do-destroy-rebuild-test-database this is assuming that they have already run: ./tools/postgres-init-db ./tools/do-destroy-rebuild-database at some point on this pg_cluster. (The ordering is important; it will other- wise complain about the south_migration table). (imported from commit c56c6f27e13df7ae10b2e643e65d669dde61af3d) 2013-05-08 05:30:42 +02:00			`./zephyr/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 "$@"`