NetBSD/tests
christos d54a6e0c5d Add blocklist support to libwrap which enables all programs using libwrap
to block access from hosts we deny. (libwrap support from Greg A. Woods)
2021-03-07 15:09:12 +00:00
..
bin PR bin/55979 2021-02-16 09:46:24 +00:00
crypto
dev
fs Add blocklist support to libwrap which enables all programs using libwrap 2021-03-07 15:09:12 +00:00
games
include
ipf
kernel
lib Adjust for conditional NLS 2021-02-25 22:37:36 +00:00
libexec
modules
net Revert previous, 11th time failed after commit. Problem must be elsewhere. 2021-03-02 07:16:24 +00:00
rump
sbin
share
sys
usr.bin tests/indent: add tests for the remaining command line options 2021-03-07 10:12:18 +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.