Mercurial > gemma

comparison schema/run_tests.sh @ 196:b67208d82543

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Make test output more comprehensive Running all tests in one transaction ensures the final output tells about any failing test, not just in the last transaction (i.e. test script). The price is that no traces of the tests are left in the database because we have to rollback in order to have no left-over test roles in the cluster.
author Tom Gottfried <tom@intevation.de>
date Fri, 20 Jul 2018 18:31:45 +0200
parents a9d9c2b1d08c
children 88d21c29cf04
comparison
equal deleted inserted replaced
195:5dc8e734487a 196:b67208d82543
7 psql -qv ON_ERROR_STOP= -d gemma_test \ 7 psql -qv ON_ERROR_STOP= -d gemma_test \
8 -f gemma.sql \ 8 -f gemma.sql \
9 -f auth.sql \ 9 -f auth.sql \
10 -f manage_users.sql 10 -f manage_users.sql
11 11
12 psql -qv ON_ERROR_STOP= -f tap_tests_data.sql -d gemma_test 12 # Add test data, run tests and ROLLBACK to prevent test roles to stay
13 13 # in cluster, which would prevent tests from being repeatable
14 psql -Xf auth_tests.sql -d gemma_test 14 psql -qXv ON_ERROR_STOP= -v AUTOCOMMIT=off -d gemma_test \
15 psql -Xf manage_users_tests.sql -d gemma_test 15 -f tap_tests_data.sql \
16 -c 'SELECT plan(22)' \
17 -f auth_tests.sql \
18 -f manage_users_tests.sql \
19 -c 'SELECT * FROM finish()' \
20 -c 'ROLLBACK'