postgresql-setup-tests.git/tester, branch master

tester: document 'run --dist' option

2015-06-08T15:26:50+00:00

* tester/run (show_help): Mention --dist.

tester/run: fix typos

2014-11-19T14:47:47+00:00

* tester/run: s/$@/$*/.
($DTF_RESULT_SUCCES): Rename to $DTF_RESULT_SUCCESS.
(info): s/SUCCES/SUCCESS/.

tester/run: fix --listonly option

2014-11-06T13:12:57+00:00

Do not try to put some output into YML file when we are only
listing.  That could cause 'Permision denied' errors even if the
permission is actually not needed.

* tester/run (__result_yml_print): New local function.
(die, run_test): Call __result_yml_print instead of hand touching
the yml file.

controller/README: reworked from top-srcdir README

2014-11-05T12:48:55+00:00

* README: Made as symlink to controller/README.
* controller/Makefile.am: Distribute the README and configuration
file template.
* controller/README: Reworked version of README following current
API.
* controller/doc/dtf-controller/OSID.sh.template: New
configuration template.
* tester/dtf-prepare-testsuite: Prepare also basic taskdir
structure.

tester/run: avoid useless error output

2014-11-05T07:16:56+00:00

* tester/run (die): Do not throw 'permission denied' message if
the die was called too early (and the result dir is still not
created).

tester/run: fix exit status handling

2014-10-27T13:03:24+00:00

* tester/run: Define 0, 1 and 2 exit status.  Also handle SKIP
test-case exit status.

tester: missing FAIL output from error handling

2014-10-24T13:55:37+00:00

* tester/run: Handle the "default" return value of 'run()' by
throwing '[  FAIL  ]' string to stdout.

tester/run: better define API

2014-10-24T12:29:35+00:00

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.

tester/controller: better test-result layout

2014-10-22T07:53:30+00:00

Make sure that on tester machine everything is put into
$DTF_RESULTDIR.  Similarly, on controller machine, everything
should be put into --workdir.

* controller/run_remote: Detect $srcdir.
(workdir_prereq): The $opt_workdir is temporary directory by
default.
* tester/run (run): Task results now go into $DTF_RESULTDIR/tasks.
The main xml result goes into $DTF_RESULT/dtf.xml.

big reorg: prepare for generalization

2014-10-22T06:54:05+00:00

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.