NetBSD/tests
riastradh cdd57aa330 tests/crypto/opencrypto: test_asymfeat requires privileges. 2023-08-05 13:29:57 +00:00
..
bin
crypto tests/crypto/opencrypto: test_asymfeat requires privileges. 2023-08-05 13:29:57 +00:00
dev
fs
games
include tests/include/t_paths: Test all paths, nonfatally. 2023-08-05 12:11:05 +00:00
ipf
kernel
lib tests/lib/librumphijack: Avoid trying to run rpcbind as non-root. 2023-08-05 13:13:37 +00:00
libexec
modules
net tests/net/inpcb: Tests require root. 2023-08-05 13:25:26 +00:00
rump
sbin
share
sys
usr.bin lint: implement __builtin_offsetof for the simplest cases 2023-08-05 10:13:39 +00:00
usr.sbin
Makefile
Makefile.inc
README
h_macros.h

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.