NetBSD/tests
2016-10-31 23:51:20 +00:00
..
bin
crypto periphereal updates and generated files for the new openssl. 2016-10-14 16:09:43 +00:00
dev pad(4) must be open before corresponding audio device is opened. 2016-10-15 07:08:06 +00:00
fs Incrase timeout for the benefit of the walk_list_user test case which 2016-10-08 13:23:53 +00:00
games
include
ipf
kernel
lib more tests from kamil 2016-10-31 23:51:20 +00:00
libexec
modules
net Add tests for ping6 options 2016-10-31 10:38:25 +00:00
rump Disable aslr too since we are playing address space range tricks. 2016-10-14 16:02:35 +00:00
sbin
share
sys
usr.bin Add tests for uniq(1) based on the example test cases provided in the POSIX man page. 2016-10-22 14:13:39 +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.