Files
zulip/zephyr/tests/generate-fixtures
Zev Benjamin a84947eade tests: Don't regenerate the test database every time we run tests
This cuts about 6 seconds off of the test startup time on my laptop.
The other startup costs are about 1 second for the server to come up
and about half a second for casperjs to begin executing tests.

generate-fixtures now takes a '--force' option that can be use to
force a regeneration of the test database.

(imported from commit 1f473507502f0edf159b2638abb392d9357eb46f)
2013-03-05 17:26:50 -05:00

30 lines
1.2 KiB
Bash
Executable File

#!/bin/sh -e
if [ -e zephyr/tests/zephyrdb.test.pristine ]; then
if [ "$1" != "--force" ]; then
cp zephyr/tests/zephyrdb.test.pristine zephyr/tests/zephyrdb.test
exit 0
fi
fi
mkdir -p zephyr/fixtures
rm -f zephyr/tests/zephyrdb.test
rm -f zephyr/tests/zephyrdb.test.pristine
# Remove time.pyc to try to prevent it from screwing people importing
# time from inside zephyr.lib. We can drop this hack after a bit.
rm -f zephyr/lib/time.pyc
python manage.py syncdb --noinput --settings=humbug.test_settings
python manage.py migrate --settings=humbug.test_settings --all
# 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
cp zephyr/tests/zephyrdb.test zephyr/tests/zephyrdb.test.pristine