tests/add-missing.tap


Log

Author Commit Date CI Message
Stefano Lattarini 5b44ce39 2012-02-23T13:07:57 tests: quote 'like this', not `like this', as per GCS recommendation This patch converts the automake testsuite and related files, to the use of new quoting format 'like this' or "like this" rather than `like this'. This is done for consistency with the new recommendations in the GNU Coding Standards, and, well, because I've come to actually prefer the '...' and "..." quoting formats over the `...' one. * tests/README: Update quoting format throughout. Remove some "excessive" use of quoting, and throw in minor rewording where appropriate. * tests/Makefile.am: Likewise, for comments. * tests/CheckListOfTests.am: Likewise. * tests/defs-static.in: Likewise. * tests/defs: Likewise. * tests/trivial-test-driver: Likewise. * Many tests/*.tap, tests/*.test and tests/*.sh files: Likewise, and for the diagnostic and informational messages as well. * tests/gen-testsuite-part: Likewise, and for the generated tests as well.
Stefano Lattarini db973eaa 2012-02-21T19:47:36 tests: prefer 'configure.ac' over 'configure.in' With this change, our testsuite now uses 'configure.ac' as the name for the typical autoconf input, instead of the obsolescent 'configure.in' (which has been deprecated for several years, at least since autoconf 2.50). Most of the test cases changed by this commit have been automatically modified with this sed command (using GNU sed): sed -i 's/\<configure\(\\\?\)\.in\>/configure\1.ac/g' * syntax-checks.mk (sc_tests_no_configure_in): New syntax check. (syntax_check_rules): Add it. * tests/defs: Create stub for autoconf input in 'configure.ac', not in 'configure.in'. Adjust comments. ($AUTOCONF, $AUTOHEADER, $AUTORECONF): Remove workaround for the infamous debian autoconf wrapper: we don't need such workaround anymore now that we name our autoconf input as 'configure.ac'. For more information, see commit v1.11-564-g63da492 "test defs: hack to support autoconf-wrapper programs" of 16-12-2011. * tests/README: Use 'configure.ac', not 'configure.in'. * Many many tests: Likewise. * tests/backcompat3.test: Adjust to avoid spurious failures. * tests/backcompat5.test: Likewise. * tests/missing6.test: Likewise. * tests/backcompat6.test: Likewise, and extend a bit since we are at it.
Stefano Lattarini 641a5a4b 2012-02-16T10:46:23 maint: run "make update-copyright"
Stefano Lattarini 21f97935 2012-02-06T22:45:47 cosmetics: few whitespace fixlets
Stefano Lattarini 7fe475b6 2012-01-08T13:36:46 tests: avoid many spurious failures on MSYS due to lack of symlinks Fixes automake bug#10441. * tests/add-missing.tap: Do not assume the system supports real symlinks, as this is not the case for MinGW/MSYS. Skip checks that would spuriously fail in that situation. * tests/copy.test: Likewise. Reported by Peter Rosin.
Stefano Lattarini e55b4ab1 2011-08-14T14:46:53 maintcheck: look for TAP-based tests without TAP plan * Makefile.am (sc_tests_tap_plan): New maintainer check. (syntax_check_rules): Add it. * tests/suffix10.tap: Declare a TAP plan. * tests/add-missing.tap: Likewise.
Stefano Lattarini 0d8a113d 2011-08-13T14:29:28 testsuite: keep more debugging info around in 'add-missing.tap' * tests/add-missing.tap: Use a different directory for each test, so that in case of failure more information is kept around. Since we are at it, remove redundant TAP diagnostic, and define `$am_create_testdir' to "empty" to avoid bringing in unused auxiliary files.
Stefano Lattarini 8be644b8 2011-08-08T15:43:53 testsuite: improve interface for giving early TAP plan Since commit `v1.11-976-g4740f56', an early TAP plan can also be specified after input lines have already been seen, as long as no one of them is a TAP result line. We can now take advantage of this in our own testsuite, allowing the TAP-based scripts to specify their earlier plan after having included `./defs'. In particular, this offers the benefit of allowing those scripts to issue a "skip all" plan (e.g., "1..0 # SKIP reason ...") after the inclusion of `./defs', which wasn't possible with the older interface (introduced in commit `v1.11-1114-g0286308'). * tests/defs: Don't try to call `plan_' if `$planned' is defined, the calling scripts can do that directly now. * tests/ac-output-old.tap: Use `plan_' directly instead of setting `$planned' before including `./defs'. * tests/automake-cmdline.tap: Likewise. * tests/depmod.tap: Likewise. * tests/instspc.tap: Likewise. * tests/tap-bad-prog.tap: Likewise. * tests/add-missing.tap: Don't set `$planned'.
Stefano Lattarini 0286308c 2011-08-07T09:42:48 testsuite: TAP tests can have early plan now * tests/defs: When using TAP, allow the user to specify the number of tests through the `$planned' variable. (trap): Do not print the auto-generated plan if an explicit one has already been printed. * tests/defs-static.in: Complain and bail out if the `$planned' variable is exported in the environment. Reformat the code to facilitate future additions. * tests/Makefile.am (TESTS_ENVIRONMENT): Neutralize `$planned'. * tests/self-check-env-sanitize.test: Update. * tests/ac-output-old.tap: Give an explicit TAP plan, by defining `$planned' just before including `./defs'. * tests/depmode.tap: Likewise. * tests/automake-cmdline.tap: Likewise. * tests/tap-bad-prog.tap: Likewise. * tests/instspc.tap: Likewise, and related adjustments. * tests/add-missing.tap: Make it explicit that we have no a-priori plan, and tell why.
Stefano Lattarini 0cf750d7 2011-08-05T22:58:03 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 obtained through some shell indirections). * tests/tap-functions.sh (diag_): Assume that the string denoting TAP diagnostic is stored in the `$diag_string_' variable. Update comments. ($diag_string_): Initialize to "#". * tests/defs ($diag_string_): Re-define to "#%#". (show_): Remove, it's obsolete now. * add-missing.tap: Don't use `show_' anymore to avoid spurious TAP diagnostic; `cat' should suffice now.
Stefano Lattarini 9b967c28 2011-08-04T11:08:24 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 at it, make its implementation more namespace-safe, and improve its command-line interface. (AUTOMAKE_fails): Adapt to the new command-line interface of `AUTOMAKE_run'. * tests/add-missing.test: Renamed ... * tests/add-missing.tap: ... to this, and converted to the use of the TAP protocol, and of the new `show_' function. * tests/automake.test: Renamed ... * tests/automake-cmdline.tap: ... to this, and converted to the use of the TAP protocol. * tests/getopt.test: Adapt to the new command-line interface of `AUTOMAKE_run'. * tests/cond44.test: Likewise. * tests/cond45.test: Likewise. * tests/configure.test: Likewise. * tests/license2.test: Likewise. * tests/parallel-am.test: Likewise. * tests/parallel-am3.test: Likewise. * tests/tags2.test: Likewise. * tests/werror3.test: Likewise. * tests/werror4.test: Likewise. * tests/amopts-variable-expansion.test: Likewise. * tests/warnings-win-over-strictness.test: Likewise. * tests/Makefile.am (TESTS): Update. (TAP_LOG_DRIVER_FLAGS): Add `--merge', so that TAP diagnostic is reported in the testsuite progress output.