NetBSD/tests
2014-08-23 16:26:13 +00:00
..
bin Run scripts at build time via ${HOST_SH} 2014-07-27 14:24:17 +00:00
crypto
dev Fix static linking for the tests: -lrump is also used by -lrumpuser, 2014-06-10 04:28:39 +00:00
fs Mark udf_lookup_complex as an expected failure, referencing PR kern/49033. 2014-08-12 12:13:09 +00:00
games
include
ipf Darren fixed n8 and n9 recently 2014-07-15 20:00:23 +00:00
kernel Merge tls-earlyentropy branch into HEAD. 2014-08-10 16:44:32 +00:00
lib Update hardcoded fd expectations now that rump kernels open 0/1/2. 2014-08-13 00:03:00 +00:00
libexec Fix static linking for the tests: -lrump is also used by -lrumpuser, 2014-06-10 04:28:39 +00:00
modules Fix static linking for the tests: -lrump is also used by -lrumpuser, 2014-06-10 04:28:39 +00:00
net Add bpfjit_cop_copx and bpfjit_copx_cop tests. 2014-07-13 21:35:33 +00:00
rump Fix static linking for the tests: -lrump is also used by -lrumpuser, 2014-06-10 04:28:39 +00:00
sbin Added test of -d option to sysctl 2014-05-16 18:50:28 +00:00
share
sys
usr.bin Remove commented-out debug code that was accidentally committed yesterday. 2014-08-23 16:26:13 +00:00
usr.sbin
h_macros.h
Makefile
Makefile.inc
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.