It has been a while since they are runnable only through "make check"
or "./runtest", and not directly.
* HACKING: Adjust.
* t/README: Likewise, and updated the surrounding text to get rid of
obsolete statements and advices.
Signed-off-by: Stefano Lattarini <stefano.lattarini@gmail.com>
* Use "make check" and "make maintainer-check" liberally.
-* Make sure each test file is executable.
-
* Export the 'keep_testdirs' environment variable to "yes" to keep
test directories for successful tests also.
by a C++ compiler, for similar reasons (i.e., the isatty(3) function
from that same unistd.h header would be required otherwise).
-* Before commit: make sure the test is executable, add the tests to
- TESTS in Makefile.am, add it to XFAIL_TESTS in addition if needed,
- write a ChangeLog entry, send the diff to <automake-patches@gnu.org>.
+* Add any new test to handwritten_TESTS in 't/list-of-tests.mk', and
+ to XFAIL_TESTS in addition if needed (that is, if the test is expected
+ to fail).
* In test scripts, prefer using POSIX constructs over their old
Bourne-only equivalents: