[FYI] {tap-testsuite-work} testsuite: use custom TAP diagnostic in our own tests

This change allow us to easily and transparently avoid spurious TAP diagnostic in our own testsuite, with the help of the new `--diagnostic-string' option of our TAP test driver. * tests/Makefile.am (TAP_LOG_DRIVER_FLAGS): Also pass option `--diagnostic-string' with value `#%#' (necessarily obtain

[FYI] {tap-testsuite-work} Merged 'test-protocols'

I've merged the 'test-protocols' branch into the 'tap-testsuite-work' protocol, and pushed. Regards, Stefano

[FYI] {test-protocols} tap: fix typo in TAP driver version message

* lib/tap-driver (anonymous subroutine printing the script version message): Add missing trailing newline to the version message. --- ChangeLog |6 ++ lib/tap-driver |2 +- 2 files changed, 7 insertions(+), 1 deletions(-) diff --git a/ChangeLog b/ChangeLog index 6036f42..b44766c

[FYI] {test-protocols} tap docs: we don't support pragma or version directives (yet)

* doc/automake.texi (Incompatibilities with other TAP parsers and drivers): Document that limitation. Normalize an unrelated "TODO" item. --- ChangeLog |7 +++ doc/automake.texi |5 - 2 files changed, 11 insertions(+), 1 deletions(-) diff --git a/ChangeLog b/ChangeLog ind

[FYI] {test-protocols} tap: new option to change the string designating TAP diagnostic

Here we introduce a new option `--diagnostic-string' in our TAP test driver, that allows the user to specify which string should denote the beginning of a TAP diagnostic line. This change is not gratuitous, nor result if over-engineering: it is motivated by real issues that have emerged during the

[PATCH] check: add small "synchronization" comment to `test-driver'

* lib/test-driver: Add comment to the code initializing ANSI color escapes, telling to keep it in sync with the similar initialization in `lib/am/check.am'. --- ChangeLog |7 +++ lib/test-driver |1 + 2 files changed, 8 insertions(+), 0 deletions(-) diff --git a/ChangeLog b/Chan

[FYI] {test-protocols} maintcheck: fix spurious failure w.r.t. use of bare "exit"

* tests/check12.test: Cosmetic changes to avoid triggering a spurious failure of the `sc_tests_Exit_not_exit' maintainer check. --- ChangeLog |7 +++ tests/check12.test | 16 2 files changed, 15 insertions(+), 8 deletions(-) diff --git a/ChangeLog b/ChangeLog i

[FYI] {test-protocols} check: update comments to reflect recent heavy changes

* lib/am/check.am [%?PARALLEL_TESTS%]: Update the comments to reflect the recent changes. Remove quite many comments that were merely duplicating excerpts from the Automake manual. --- ChangeLog |7 +++ lib/am/check.am | 31 ++- 2 files changed, 13 inse

[FYI] {test-protocols} check: small cleanups and refactorings in test harness and drivers

* lib/tap-driver (yn): New subroutine, converts a boolean value to a "yes" or "no" string. (write_test_results): Use it, and related reformatting. * lib/test-driver (trap): Also remove the `.trs' file on signals, for extra safety. (fatal): Remove this function, it's never used. ($logfile, $trsfile)

[FYI] {tap-testsuite-work} testsuite: more correct names for a couple of tests

* tests/parallel-tests-ext-driver.test: Rename ... * tests/parallel-tests-log-compiler-1.test: ... to this, and adjust heading comments. * tests/parallel-tests-ext-driver-prog.test: Rename ... * tests/parallel-tests-log-compiler-2.test: ... to this, and adjust heading comments. * tests/Makefile.am

[FYI] {tap-testsuite-work} testsuite: fix another spurious failure

* tests/parallel-tests-ext-driver.test: Name out custom/dummy log compilers as `foo-compiler' rather `foo-driver'; not only this is less confusing, it also avoids errors due to the dummy log compiler `test-driver' overriding the `test-driver' helper script installed by Automake. * tests/parallel-te

[FYI] {tap-testsuite-work} testsuite: fix a spurious failure

* tests/parallel-tests-ext-driver.test: Exporting of environment variables directly from $(LOG_COMPILER) variables is not allowed anymore. Adjust to this. --- ChangeLog|7 +++ tests/parallel-tests-ext-driver.test | 14 ++ 2 files changed, 9 insert

[FYI] {tap-testsuite-work} testsuite: yet more use of TAP, and related extensions

* tests/defs (show_): New function, display the contents of one or more files on stdout, with bells & whistles (both for cosmetic and practical reasons, the latter aimed at avoiding spurious TAP diagnostic). (AUTOMAKE_run): Extend and adapt to make it compatible with TAP based tests. Since we are

[FYI] {test-protocosl} testsuite: use AM_TESTS_FD_REDIRECT where appropriate

* parallel-tests-interrupt.test: Use AM_TESTS_FD_REDIRECT, not AM_TESTS_ENVIRONMENT, to define file descriptors' redirection for "make check". Fix botched comment. --- ChangeLog |7 +++ tests/parallel-tests-interrupt.test |4 ++-- 2 files changed, 9 insertion

[FYI] {test-protocols} docs: some fixlets in documentation on testsuites support

* doc/automake.texi (Script-based Testsuites): Rename node ... (Scripts-based Testsuites): ... to this. Break overly long lines in an example (were causing problems with PDF output). (Parallel Test Harness): Don't intend paragraphs that come after examples or bulleted list. (Overview of Custom Tes

[FYI] {test-protocols} test harness: be aware of more metadata, simplify test drivers

I've already pushed this patch, but reviews are still welcome; I will do any required amendment in follow-up changes. Regards, Stefano From 956c58ab490f79be1829ac4fc3a0da58a4b30973 Mon Sep 17 00:00:00 2001 Message-Id: <956c58ab490f79be1829ac4fc3a0da58a4b30973.1312532758.git.stefano.lattar...@gma