NetBSD/tests
2017-08-21 17:11:18 +00:00
..
bin Make the $'...' syntax tests test what is supposed to work, rather than 2017-08-21 00:56:22 +00:00
crypto constify more to avoid gcc stupidity. 2017-06-14 21:43:02 +00:00
dev Remove MKCRYPTO option. 2017-05-21 15:28:36 +00:00
fs give it more time. 2017-05-24 15:29:51 +00:00
games
include
ipf
kernel
lib don't skip nexttoward for aarch64 and mips64 2017-08-21 17:11:18 +00:00
libexec Add sparc/sparc64 support for irelative relocations. 2017-08-12 09:03:27 +00:00
modules
net Add support IP_PKTINFO for sendmsg(2). 2017-08-10 04:31:58 +00:00
rump Fix detection of expected results. The rump kernel code apparently 2017-05-03 12:09:41 +00:00
sbin
share
sys
usr.bin Do the previous test a better way - for a file, test is generally 2017-07-25 22:28:22 +00:00
usr.sbin
h_macros.h
Makefile Remove MKCRYPTO option. 2017-05-21 15:28:36 +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.