NetBSD/tests
2013-04-16 22:05:44 +00:00
..
bin
crypto
dev The sh api calls it atf_expect_fail, while the c api calls it 2013-04-14 16:07:46 +00:00
fs
games
include
ipf Fix argument order for "n14" 2013-03-19 13:23:58 +00:00
kernel First attempt at stress testing umount of a busy disk. 2013-04-16 22:05:44 +00:00
lib Backout previous - which did not include the change described in the log 2013-04-14 16:03:06 +00:00
libexec
modules
net
rump
sbin
share
sys
usr.bin don't run with -n if you expect protocol translation from number to name. 2013-04-07 19:14:03 +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.