NetBSD/tests
2013-11-22 17:19:14 +00:00
..
bin
crypto
dev
fs fix unused variable warnings 2013-10-19 17:45:00 +00:00
games
include fix unused variable warnings 2013-10-19 17:45:00 +00:00
ipf
kernel fix unused variable warnings 2013-10-19 17:45:00 +00:00
lib Adjust expected epsilon for sqrtl <-> powl comparisions for defects in 2013-11-22 17:19:14 +00:00
libexec
modules
net CID 1107543, 230676, 1107543, 976795, 230676, 976795, 1125885, etc. 2013-11-13 21:41:23 +00:00
rump
sbin
share
sys
usr.bin
usr.sbin adjust output now that we don't output size info for links and directories 2013-10-20 17:27:37 +00:00
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.