NetBSD/tests
joerg 44c2dc6e5d Make back trace more robust. At least on i386, one of the intermediate
functions in ATF is not replaced by tail recursion elimination, so
mark it as optional.
2013-06-06 17:40:09 +00:00
..
bin
crypto
dev
fs
games
include
ipf Mark two more test case as only failing for BE 2013-05-16 07:43:02 +00:00
kernel Don't rely on "kill -0" to check whether a background shell command 2013-05-31 14:40:48 +00:00
lib Make back trace more robust. At least on i386, one of the intermediate 2013-06-06 17:40:09 +00:00
libexec
modules
net
rump
sbin
share
sys
usr.bin PR/47825: Garrett Cooper: Fix hardcoding of NetBSD in t_grep.sh 2013-05-17 15:39:17 +00:00
usr.sbin
Makefile
Makefile.inc
README
h_macros.h PR/47826: Garrett Cooper: Add <sys/types.h>. Really I am tempted to remove 2013-05-17 15:42:09 +00:00

README

$NetBSD: README,v 1.4 2012/05/18 15:36:21 jruoho Exp $

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

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.