NetBSD/tests
2016-05-28 14:38:29 +00:00
..
bin Use valid (standard) shell syntax, in anticipation of /bin/sh enforcing 2016-05-17 09:05:14 +00:00
crypto
dev Use rump_schedule() before calling things in the rump context. 2016-05-05 17:40:26 +00:00
fs
games
include
ipf
kernel Test for PR kern/51135 is no longer failing. 2016-05-22 04:34:44 +00:00
lib Fix mprotect for the helper. 2016-05-28 14:38:29 +00:00
libexec
modules
net Disable PAX mprotect to make just-in-time-compile tests work again. 2016-05-24 10:16:34 +00:00
rump
sbin
share
sys
usr.bin
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.