[src/trunk]: src/tests Clarify this a little.

[jruoho <jruoho%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/1c75f4f0eef8
branches:  trunk
changeset: 779322:1c75f4f0eef8
user:      jruoho <jruoho%NetBSD.org@localhost>
date:      Fri May 18 15:36:21 2012 +0000

description:
Clarify this a little.

diffstat:

 tests/README |  21 +++++++++++++++------
 1 files changed, 15 insertions(+), 6 deletions(-)

diffs (30 lines):

diff -r 4804afcb12b9 -r 1c75f4f0eef8 tests/README
--- a/tests/README      Fri May 18 15:25:25 2012 +0000
+++ b/tests/README      Fri May 18 15:36:21 2012 +0000
@@ -1,11 +1,20 @@
-$NetBSD: README,v 1.3 2012/02/13 08:55:20 wiz Exp $
+$NetBSD: README,v 1.4 2012/05/18 15:36:21 jruoho Exp $
+
+When adding new tests, please try to follow the following conventions.
 
-When adding new tests, please try to follow the directory structure of
-the real source tree. For instance, interfaces available via the C library
-should follow:
+1. For library routines, including system calls, the directory structure of
+   the tests should follow the directory structure of the real source tree.
+   For instance, interfaces available via the C library should follow:
 
        src/lib/libc/gen -> src/tests/lib/libc/gen
        src/lib/libc/sys -> src/tests/lib/libc/sys
+       ...
 
-Equivalently, tests for a program residing in src/usr.bin/program should be
-added to the src/tests/usr.bin/program subdirectory.
+2. Equivalently, all tests for userland utilities should try to follow their
+   location in the source tree. If this can not be satisfied, the tests for
+   a utility should be located under the directory to which the utility is
+   installed. Thus, a test for env(1) should go to src/tests/usr.bin/env.
+   Likewise, a test for tcpdump(8) should be in src/tests/usr.sbin/tcpdump,
+   even though the source code for the program is located under src/external.
+
+3. Otherwise use your own discretion.