zulip/zephyr/tests/generate-fixtures

#!/bin/sh -e
mkdir -p zephyr/fixtures
rm -f zephyr/tests/zephyrdb.test
python manage.py syncdb --noinput --settings=humbug.test_settings
# This next line can be simplified to "-n0" once we fix our app with 0 messages.
python manage.py populate_db --settings=humbug.test_settings --test-suite -n2 \
    --threads=1 --huddles=0 --personals=0 --percent-huddles=0 --percent-personals=0
python manage.py dumpdata  --settings=humbug.test_settings \
    auth.User zephyr.UserProfile zephyr.Stream zephyr.Recipient \
    zephyr.Subscription zephyr.Message zephyr.Huddle zephyr.Realm \
    zephyr.UserMessage zephyr.Client \
    zephyr.DefaultStream > zephyr/fixtures/messages.json
test: Fail if generate-fixtures fails (imported from commit b13167ad04837cfeb64989ff43fec2e6ae890a33) 2012-11-02 22:20:39 +01:00			`#!/bin/sh -e`
Remove fixtures from version control. (imported from commit 32f17aa1b674e47d730a00cced8b5bed8a136755) 2012-09-04 22:31:56 +02:00			`mkdir -p zephyr/fixtures`
Fix removal of stale zephyrdb.test files. (imported from commit 2f3f8b1f05d43ed2fe9e3b5427f0be2e2b05b51b) 2012-10-11 00:12:27 +02:00			`rm -f zephyr/tests/zephyrdb.test`
Rename test-settings.py to test_settings.py (imported from commit c9ad55821bc66a7c11668ac0b40ca13c2e05986e) 2012-10-11 00:10:48 +02:00			`python manage.py syncdb --noinput --settings=humbug.test_settings`
Make the Django-based test suite much faster. So, I got annoyed that our test suite was taking forever to run: real 2m13.443s user 1m32.630s sys 0m3.748s Some quick profiling determined that the test suite is spending all of its time loading the fixtures files (zephyr/fixtures/messages.json) that it loads for each test case (3s to load that for each test case). To improve this situation, I cut out from the test database used by the test suite most of the users, subscriptions, etc. that aren't being used directly by the test cases. The impact is a quite significant speedup: real 0m15.176s user 0m9.161s sys 0m0.508s We're still spending over a quarter of a second per test, which isn't great -- but this is at least no longer unbearable. This commit doesn't make any changes to the populate_db output if you don't pass the new --test-suite option. (imported from commit 2334ba5399b33edab3d29ff269fde4ea77ccd48e) 2013-01-08 21:59:52 +01:00			`# This next line can be simplified to "-n0" once we fix our app with 0 messages.`
			`python manage.py populate_db --settings=humbug.test_settings --test-suite -n2 \`
			`--threads=1 --huddles=0 --personals=0 --percent-huddles=0 --percent-personals=0`
Wrap some other extremely long lines (imported from commit e7d55f318c8865ca953bf4520d1b07f7e84a4aeb) 2012-10-25 06:11:28 +02:00			`python manage.py dumpdata --settings=humbug.test_settings \`
			`auth.User zephyr.UserProfile zephyr.Stream zephyr.Recipient \`
			`zephyr.Subscription zephyr.Message zephyr.Huddle zephyr.Realm \`
[schema] Add a management script to create default streams for a domain. Run this script on an existing realm to create or change default streams, which new users will get upon account creation. (imported from commit 8938dcbd3520d97d25b4c6ca783d35c9aef52df0) 2012-11-27 18:26:51 +01:00			`zephyr.UserMessage zephyr.Client \`
			`zephyr.DefaultStream > zephyr/fixtures/messages.json`