NetBSD/tests
2017-12-24 17:37:23 +00:00
..
bin Add a test case for "set -X". 2017-11-16 19:41:41 +00:00
crypto
dev Fix fallout from hid factorisation: 2017-12-10 20:38:13 +00:00
fs ATF test program for PR kern/52738: check for mtime updates after rewriting 2017-11-19 21:05:26 +00:00
games
include
ipf
kernel Use SCRIPTS instead of PROGS to avoid strip(1) if STRIPFLAG=-s. 2017-12-14 14:38:17 +00:00
lib fix priority tests for SCHED_OTHER 2017-12-24 17:37:23 +00:00
libexec
modules
net Adjust outputs of route's flags to include a numeric output 2017-12-18 04:11:46 +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.