Aren/NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Clarify this a little.

Browse Source
This commit is contained in:
jruoho 2012-05-18 15:36:21 +00:00
parent af62c3b4d8
commit 63e8388028
1 changed files with 15 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
tests/README
View File

@ -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 directory structure of
the real source tree. For instance, interfaces available via the C library
should follow:
When adding new tests, please try to follow the following conventions.
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.