summaryrefslogtreecommitdiffstats
path: root/postgresql-tests
Commit message (Collapse)AuthorAgeFilesLines
* postgresql-tests: use different internal data mirrorPavel Raiskup2014-10-241-1/+1
| | | | * postgresql-tests/config.sh: Use office accessible IP.
* tester/run: better define APIPavel Raiskup2014-10-249-47/+64
| | | | | | | | | | | | | | | | | | | | | | | Define test return values and its calling. Do not split the testcase into configuration and running script, rather use one file and wrap the script by run() method. This is still very easy to run without running whole testsuite. * tester/run (DTF_RESULT_*): Return values API. (run): Rename to run_test. Make the function more readable, don't generate xml results (not yet used anyway). * postgresql-tests/config.sh: Do not source the per-testsuite library directly as the configuration script config.h is sourced even by 'run' script itself for --dist option (for that action we actually do not need per-testsuite libraries). * postgresql-tests/tasks/initdb/runtest.sh: New API used. * postgresql-tests/tasks/initdb_old/runtest.sh: Likewise. * postgresql-tests/tasks/upgrade-basic/runtest.sh: Likewise. * postgresql-tests/tasks/upgrade-utf8-syntax/runtest.sh: Likewise. * postgresql-tests/tasks/upgrade-basic/config.sh: Remove. * postgresql-tests/tasks/initdb/config.sh: Remove. * postgresql-tests/tasks/initdb_old/config.sh: Remove. * postgresql-tests/tasks/upgrade-utf8-syntax/config.sh: Remove.
* postgresql-tests: data "mirroring" supportPavel Raiskup2014-10-224-3/+19
| | | | | | | | | | | | | | | Turns out that our OpenStack has poor connectivity to Brno so I added data mirror on one VM on OS1. * postgresql-tests/lib_pgsql.sh (dtf_postgresql_data_mirror): New PostgreSQL related API. * postgresql-tests/config.sh ($dtf_dataurl): Removed PG API variable. ($dtf_dataurls): Substitution for $dtf_dataurl; Array of possible data URLs. * postgresql-tests/tasks/upgrade-basic/runtest.sh: Reuse new PG API^. * postgresql-tests/tasks/upgrade-utf8-syntax/runtest.sh: Likewise.
* big reorg: prepare for generalizationPavel Raiskup2014-10-2224-0/+458
Try to split into three separate components -> controller, tester, and 'tasks' (postgresql-tasks in our case). The controller component is the main part which is able to run the task remotely. Tester is more-like library for 'tasks' component (should be reusable on the raw git level). * controller: Almost separated component. * postgresql-tasks: Likewise. * tester: Likewise.