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.lattar...@gmail.com> --- HACKING | 2 -- t/README | 6 +++--- 2 files changed, 3 insertions(+), 5 deletions(-) diff --git a/HACKING b/HACKING index cebcb72..3ce2e66 100644 --- a/HACKING +++ b/HACKING @@ -264,8 +264,6 @@ * 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. diff --git a/t/README b/t/README index 02cb3a5..60eb7c7 100644 --- a/t/README +++ b/t/README @@ -254,9 +254,9 @@ Writing test cases 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: -- 1.8.3.rc2
