NetBSD/tests
2016-06-18 12:12:09 +00:00
..
bin Add a unit test for PR bin/51250 called se_output. se_output checks the output of cat 2016-06-16 01:04:58 +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 Use rump_schedule() before calling things in the rump context. 2016-05-05 17:40:26 +00:00
fs Cite a relevant PR for msdos_renamerace instead of one that was fixed 2016-05-04 08:30:22 +00:00
games
include Introduce pserialize-safe linked lists. 2016-04-09 04:39:46 +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 Test for PR kern/51135 is no longer failing. 2016-05-22 04:34:44 +00:00
lib Link static test program with LDSTATIC to deal with PIE. 2016-06-18 12:12:09 +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 Disable PAX mprotect to make just-in-time-compile tests work again. 2016-05-24 10:16:34 +00:00
rump include <stdbool.h> for bool 2016-01-25 12:21:42 +00:00
sbin When deadbeef is treated as a 32-bit signed integer, it actually has a 2016-06-17 03:55:35 +00:00
share When no gcc but clang can be found, fallback to the latter instead of 2016-03-12 08:55:54 +00:00
sys Add casts for big endian machines 2014-12-03 13:10:49 +00:00
usr.bin remove some unused test cases 2016-06-01 14:52:56 +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.