testsuite: TAP tests can have early plan now
authorStefano Lattarini <stefano.lattarini@gmail.com>
Sun, 7 Aug 2011 07:42:48 +0000 (09:42 +0200)
committerStefano Lattarini <stefano.lattarini@gmail.com>
Sun, 7 Aug 2011 09:37:32 +0000 (11:37 +0200)
commit0286308c4923e9b1547811587988fbec73aabf00
tree7f64775c82b72ea8cdad09e346eb9b5aae1a6ac1
parent7fb047693f4f820960605a681e6a8f1687dc4a9f
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.
12 files changed:
ChangeLog
tests/Makefile.am
tests/Makefile.in
tests/ac-output-old.tap
tests/add-missing.tap
tests/automake-cmdline.tap
tests/defs
tests/defs-static.in
tests/depmod.tap
tests/instspc.tap
tests/self-check-env-sanitize.test
tests/tap-bad-prog.tap