diff options
| author | Pádraig Brady <P@draigBrady.com> | 2009-02-12 13:51:03 +0000 |
|---|---|---|
| committer | Pádraig Brady <P@draigBrady.com> | 2009-02-13 11:13:33 +0000 |
| commit | 48cae1e8642684f0103848b84d5884d1ba2412c8 (patch) | |
| tree | 1845ae20d9e6f76bc906f7291fa91f33b4b1a656 /HACKING | |
| parent | 022889a4575390b656abf89b0e8f43ef03c1cc00 (diff) | |
| download | coreutils-48cae1e8642684f0103848b84d5884d1ba2412c8.tar.gz | |
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.
Diffstat (limited to 'HACKING')
| -rw-r--r-- | HACKING | 4 |
1 files changed, 3 insertions, 1 deletions
@@ -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 |