From 48cae1e8642684f0103848b84d5884d1ba2412c8 Mon Sep 17 00:00:00 2001 From: Pádraig Brady Date: Thu, 12 Feb 2009 13:51:03 +0000 Subject: maint: mention how to run a single test in HACKING docs * HACKING: Give an example of how to run a test in isolation. * README: Fix/simplify example for running a single test. * README-hacking: Reference the HACKING file. --- HACKING | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'HACKING') diff --git a/HACKING b/HACKING index 6eb04804b..2869c03e6 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: + + (cd tests && make check TESTS=misc/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 -- cgit v1.2.3-70-g09d2