NetBSD/tests
2014-09-18 15:13:27 +00:00
..
bin Visit the Bureau of Redundancy Department. 2014-09-11 18:25:30 +00:00
crypto
dev
fs Mark v7fs_lstat_symlink as an expected failure, referencing PR kern/48864. 2014-09-09 06:51:00 +00:00
games
include
ipf
kernel
lib add null and empty tests. 2014-09-08 19:01:03 +00:00
libexec Really revert to the original version. 2014-08-26 17:13:42 +00:00
modules
net Add net/if_bridge test 2014-09-18 15:13:27 +00:00
rump On systems that have only 32M of memory, the stress_short and 2014-08-30 12:14:17 +00:00
sbin
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.