Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/tools/setup/generate-fixtures

16 lines
419 B
Plaintext
Raw Normal View History

Add support for running OpenBSD in development environment.
2016-01-12 13:08:43 +01:00
#!/usr/bin/env bash
set -e
generate-fixtures: Run after schema changes even without --force. (imported from commit 1daff2ee6746c4036c3cc71746ad59e18b5a331e)
2013-04-01 23:02:24 +02:00
db tools: Refactor generate-fixtures/rebuild-test-database. So `generate-fixtures` only ever did 9 lines of code (really 3 lines of actual code) in its normal mode of operation. But it was cluttered with lots of stuff that really only happened when you called it with the `-force` option, which was only invoked by `rebuild-test-database`. Now we inline most of the code into `rebuild-test-database`. And now `generate-fixtures` is simple (and doesn't support a `-force` flag.
2020-04-22 01:39:46 +02:00
run()
generate-fixtures: Extract zulip_test_template creation as a function. This will be helpful in the upcoming changes which will make use of this extracted function to re-create zulip_test_template after migrating zulip_test db so that we have latest schema in tests.
2018-07-06 16:17:52 +02:00
{
terminate-psql-sessions: Rely on the caller to set PGHOST, PGUSER. Signed-off-by: Anders Kaseorg <anders@zulip.com>
2020-06-16 01:36:02 +02:00
PGHOST=localhost PGUSER=zulip \
"$(dirname "$0")/../../scripts/setup/terminate-psql-sessions" zulip_test zulip_test_base zulip_test_template
scripts: Always use ON_ERROR_STOP=1 when running psql. Also use psql -e (--echo-queries) in scripts that use ‘set -x’, so errors can be traced to a specific query from the output. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-04-02 01:00:57 +02:00
psql -v ON_ERROR_STOP=1 -h localhost postgres zulip_test << EOF
generate-fixtures: Be more robust to databases being missing (imported from commit f42d673c433b8d3df4af79159831e57f5db1ee1c)
2014-01-30 23:40:07 +01:00
DROP DATABASE IF EXISTS zulip_test;
[manual] Change references to the humbug_test user, schema, and database to zulip_test This requires no changes in production, but is tagged as manual to remind developers that they need to edit and run the tools/migrate-db script to fix up their local database instances. (imported from commit fbf764fb61592ef994d6d2ad56edad65ff01f14b)
2013-10-26 04:24:40 +02:00
CREATE DATABASE zulip_test TEMPLATE zulip_test_template;
[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
EOF
flush-memcached: Respect MEMCACHED_LOCATION; handle errors. Fixes #13238. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-10-01 23:42:35 +02:00
"$(dirname "$0")/../../scripts/setup/flush-memcached"
db tools: Refactor generate-fixtures/rebuild-test-database. So `generate-fixtures` only ever did 9 lines of code (really 3 lines of actual code) in its normal mode of operation. But it was cluttered with lots of stuff that really only happened when you called it with the `-force` option, which was only invoked by `rebuild-test-database`. Now we inline most of the code into `rebuild-test-database`. And now `generate-fixtures` is simple (and doesn't support a `-force` flag.
2020-04-22 01:39:46 +02:00
}
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 23:08:55 +01:00
db tools: Refactor generate-fixtures/rebuild-test-database. So `generate-fixtures` only ever did 9 lines of code (really 3 lines of actual code) in its normal mode of operation. But it was cluttered with lots of stuff that really only happened when you called it with the `-force` option, which was only invoked by `rebuild-test-database`. Now we inline most of the code into `rebuild-test-database`. And now `generate-fixtures` is simple (and doesn't support a `-force` flag.
2020-04-22 01:39:46 +02:00
run