diff options
| author | Jim Meyering <meyering@redhat.com> | 2010-04-16 08:42:47 +0200 |
|---|---|---|
| committer | Jim Meyering <meyering@redhat.com> | 2010-04-16 08:42:47 +0200 |
| commit | 56fce1aed76fa8d2ceaff8a9c4046204493adffe (patch) | |
| tree | 6cfcdcd46d5422d5103b31e9c20a99cca4e08703 /HACKING | |
| parent | 36cc6ac787d3c8f98c88cfe14c42fe27027b785b (diff) | |
| download | coreutils-56fce1aed76fa8d2ceaff8a9c4046204493adffe.tar.xz | |
* 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
Diffstat (limited to 'HACKING')
| -rw-r--r-- | HACKING | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -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 |