NetBSD/tests
yamaguchi 0c15ac9ed3 Added missing waiting for DAD completion 2021-05-06 01:09:43 +00:00
..
bin PR bin/55979 2021-02-16 09:46:24 +00:00
crypto
dev config_found_ia() -> config_found(). 2021-04-25 05:33:20 +00:00
fs Add blocklist support to libwrap which enables all programs using libwrap 2021-03-07 15:09:12 +00:00
games simplify: use two arguments again, suggested by kre@ 2020-10-11 18:43:50 +00:00
include
ipf
kernel Avoid hard-coding names and limits so this will not break again. 2020-10-31 14:57:02 +00:00
lib Add test for POSIX_SPAWN_RESETIDS flag 2021-05-02 11:18:11 +00:00
libexec
modules
net Added missing waiting for DAD completion 2021-05-06 01:09:43 +00:00
rump for the busypage test, replace atf_tc_expect_fail() with atf_tc_skip() 2021-01-22 22:03:01 +00:00
sbin apply this change to a a couple more tests: 2020-12-10 08:16:59 +00:00
share
sys add some new uses of existing GCC_NO_* variables for warning issues. 2021-04-12 02:54:07 +00:00
usr.bin tests/lint: make test for message 118 platform-independent 2021-05-04 19:57:56 +00:00
usr.sbin don't run the "offline" or "nointr" tests by default. they exercise 2021-04-12 01:18:13 +00:00
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.