summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorDaniel Friesel <derf@finalrewind.org>2019-04-18 15:03:27 -0400
committerDaniel Friesel <derf@finalrewind.org>2019-04-18 15:03:27 -0400
commitf7db1c6a2642238b440aba39ee7e9133dfd1e901 (patch)
treee66fd9e6a74f736d33f10d71e962093de9597667 /README.md
parent4aa83625d3b6e05e8c2a48e1a70f0b4618ba63da (diff)
Update test section in README
Diffstat (limited to 'README.md')
-rw-r--r--README.md14
1 files changed, 5 insertions, 9 deletions
diff --git a/README.md b/README.md
index be398b3..8bdf03b 100644
--- a/README.md
+++ b/README.md
@@ -149,15 +149,11 @@ Testing
---
The test scripts assume that travelynx.conf contains a valid database
-connection. However, they will override db.user to `travelynx_temp`. This
-must be an account which has the same password as the one specified in
-travelynx.conf, but uses a temporary schema. This way, tests will always
-start from a clean slate and will not leave any trace in the database.
+connection. They will create a test-specific schema, perform all operations in
+it, and then drop the schema. As such, the database specified in the config is
+not affected.
-Create this account as follows:
-
-* `createuser -P travelynx_temp` (enter the password you are using for the
- regular development user)
-* from inside a psql admin shell: `alter role travelynx_temp set search_path = pg_temp;`
+Nevertheless, bugs may happen. Do NOT run tests on your production database.
+Please use a separate development database instead.
Run the tests by executing `prove`.