From 56fce1aed76fa8d2ceaff8a9c4046204493adffe Mon Sep 17 00:00:00 2001 From: Jim Meyering Date: Fri, 16 Apr 2010 08:42:47 +0200 Subject: [PATCH] * HACKING (Add tests): Change example name, "newtest" to "new-test". Not that anyone would confuse with something newt-related, but just because it is more readable that way. doc: tweak HACKING --- HACKING | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/HACKING b/HACKING index a6589d3..fe8ac43 100644 --- a/HACKING +++ b/HACKING @@ -411,9 +411,9 @@ Nearly every significant change must be accompanied by a test suite addition that exercises it. If you fix a bug, add at least one test that fails without the patch, but that succeeds once your patch is applied. If you add a feature, add tests to exercise as much of the new code -as possible. Note to run tests/misc/newtest in isolation you can do: +as possible. Note to run tests/misc/new-test in isolation you can do: - (cd tests && make check TESTS=misc/newtest VERBOSE=yes) + (cd tests && make check TESTS=misc/new-test VERBOSE=yes) There are hundreds of tests in the tests/ directories. You can use tests/sample-test as a template, or one of the various Perl-based ones -- 2.7.4