I was wondering how to do this so I'm adding this info. cheers, Pádraig.
>From 47b11fea893e3d11771abbe53144052d4bb87d2b Mon Sep 17 00:00:00 2001 From: =?utf-8?q?P=C3=A1draig=20Brady?= <p...@draigbrady.com> Date: Thu, 12 Feb 2009 13:51:03 +0000 Subject: [PATCH] maint: mention how to run a single test in HACKING docs
* HACKING: Give an example of how to run a test in isolation. * README-hacking: Reference the HACKING file. --- HACKING | 4 +++- README-hacking | 1 + 2 files changed, 4 insertions(+), 1 deletions(-) diff --git a/HACKING b/HACKING index 6eb0480..c8e85f8 100644 --- a/HACKING +++ b/HACKING @@ -288,7 +288,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. +as possible. Note to run tests/misc/newtest in isolation you can do: + + make check -C tests TESTS=newtest 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 diff --git a/README-hacking b/README-hacking index 8333cd0..7a8b4c4 100644 --- a/README-hacking +++ b/README-hacking @@ -2,6 +2,7 @@ These notes intend to help people working on the checked-out sources. These requirements do not apply when building from a distribution tarball. +See also HACKING for more detailed coreutils contribution guidlines. * Requirements -- 1.5.3.6
_______________________________________________ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
