1
0
mirror of git://git.sv.gnu.org/coreutils.git synced 2026-02-12 18:32:08 +02:00

* 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
This commit is contained in:
Jim Meyering
2010-04-16 08:42:47 +02:00
parent 36cc6ac787
commit 56fce1aed7

View File

@@ -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