NetBSD/tests
pgoyette 3ce5310bf2 Now that we have a PR for the brokenness in "ipftest -P -N", mark the
related tests as Expected Failure rather than just skipping the tests.
2012-12-01 04:40:00 +00:00
..
bin
crypto
dev
examples
fs Add fsbsizeovermaxbsize test that tests mouting a FS with block size greater 2012-11-27 16:01:49 +00:00
games
include
ipf Now that we have a PR for the brokenness in "ipftest -P -N", mark the 2012-12-01 04:40:00 +00:00
kernel Unbreak the NOTE_TRACK event of EVFILT_PROC. When attaching to the child 2012-11-17 21:55:24 +00:00
lib Skip kqueue_unsupported_fd if the drvctl device is not present. 2012-11-29 09:13:44 +00:00
libexec
modules
net Try to make this test gracefully fail when npftest is not available 2012-09-18 08:28:15 +00:00
rump
sbin
share
sys
usr.bin descend into netpgpverify test directory too 2012-11-20 08:02:06 +00:00
usr.sbin
Atffile
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.