NetBSD/tests
2016-03-10 22:30:57 +00:00
..
bin Set TEST_SH 2016-03-10 22:30:57 +00:00
crypto For the skipped ARC4 test, don't bother trying to run the test clean-up 2015-12-26 07:10:03 +00:00
dev Fix soft volume audio distortion. OK jmcneil@. 2016-02-26 13:08:28 +00:00
fs The test for PR 50608 works now, remove the expected failure. 2016-01-28 10:10:09 +00:00
games
include Define _KERNTYPES for things that need it. 2016-01-23 21:22:45 +00:00
ipf Remove the "expected failure" from test n12, and change it not to use 2015-12-26 08:01:58 +00:00
kernel This needs _KERNTYPES on some platforms. 2016-02-15 14:59:38 +00:00
lib libc fallback is known to not produce nice alias entries. Avoid spurious 2016-03-08 08:34:17 +00:00
libexec Really revert to the original version. 2014-08-26 17:13:42 +00:00
modules Define _KERNTYPES for things that need it. 2016-01-23 21:22:45 +00:00
net make it work on linux, be pickier about errors, and correct variable type. 2016-03-04 18:52:01 +00:00
rump include <stdbool.h> for bool 2016-01-25 12:21:42 +00:00
sbin Require the boot block to be used, test can't work otherwise. 2016-03-08 08:04:48 +00:00
share Hook Lutok into the build. This is all protected by the MKKYUA guard. 2013-02-16 21:40:05 +00:00
sys Add casts for big endian machines 2014-12-03 13:10:49 +00:00
usr.bin Add an anonymous struct test 2015-10-14 16:32:55 +00:00
usr.sbin t_tcpdump: skip bridges 2014-09-20 06:08:07 +00:00
h_macros.h cast and mask is overkill. 2015-01-14 22:57:27 +00:00
Makefile Don't build tests that depend on RUMP if BSD_MK_COMPAT_FILE is defined. 2015-06-22 00:05:23 +00:00
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.