summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorAssaf Gordon <assafgordon@gmail.com>2012-12-06 09:58:10 +0000
committerPádraig Brady <P@draigBrady.com>2012-12-06 09:58:55 +0000
commiteac397efff2810bbffc0857e5c2ad96d637debbe (patch)
treeb1b73da1b0f11b213fb6e001481ab21673aca178 /HACKING
parent64b8751813234b49277296a2f9bfbc64a5676274 (diff)
downloadcoreutils-eac397efff2810bbffc0857e5c2ad96d637debbe.tar.xz
maint: adjust HACKING instructions to run a single test
* HACKING: Adjust as per the recent changes introduced when switching to non recursive make.
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING6
1 files changed, 4 insertions, 2 deletions
diff --git a/HACKING b/HACKING
index de8cd7bd8..f3f961a2a 100644
--- a/HACKING
+++ b/HACKING
@@ -438,9 +438,11 @@ 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/new-test in isolation you can do:
+as possible. If you add a new test file (as opposed to adding a test to
+an existing test file) add the new test file to 'tests/local.mk'.
+Note to run tests/misc/new-test in isolation you can do:
- (cd tests && make check TESTS=misc/new-test VERBOSE=yes)
+ make TESTS=tests/misc/new-test SUBDIRS=. VERBOSE=yes
Variables that are significant for tests with their default values are: