NetBSD/tests
kamil a9391cc9b5 Fix typo in ATF test t_strtoi.c
No functional change.
2017-04-28 19:01:01 +00:00
..
bin PR bin/52090 - the $* tests are no longer expected to fail. 2017-03-20 11:48:41 +00:00
crypto add opencrypto atf for CRYPTO_3DES_CBC and CRYPTO_AES_CBC(=CRYPTO_RIJNDAEL128_CBC). 2017-04-17 03:59:37 +00:00
dev Do not assume an all-zeroes disk label will read back as a disk with 2017-03-15 10:53:15 +00:00
fs Gotta mark crashes on signal separately from failures... 2017-04-14 01:30:38 +00:00
games
include Don't play with "../.." in includes for h_macros.h; deal with it centrally. 2017-01-13 21:30:39 +00:00
ipf
kernel Stress rump hyperentropy a little harder. 2017-04-16 18:24:23 +00:00
lib Fix typo in ATF test t_strtoi.c 2017-04-28 19:01:01 +00:00
libexec Don't play with "../.." in includes for h_macros.h; deal with it centrally. 2017-01-13 21:30:39 +00:00
modules Don't play with "../.." in includes for h_macros.h; deal with it centrally. 2017-01-13 21:30:39 +00:00
net Test transport mode as well as tunnel mode 2017-04-27 10:17:12 +00:00
rump Don't play with "../.." in includes for h_macros.h; deal with it centrally. 2017-01-13 21:30:39 +00:00
sbin Skip the "migrate" test on architectures not natively using MBR, it 2017-03-22 19:13:40 +00:00
share
sys convention about function names for predicate checking: 2016-12-22 08:15:20 +00:00
usr.bin If we are using the pad audio device, there must be a process with 2017-04-20 00:17:11 +00:00
usr.sbin PR/51876: Ngie Cooper: kyua 0.11 $TMPDIR fixes 2017-01-14 20:45:16 +00:00
h_macros.h
Makefile
Makefile.inc better name 2017-01-14 01:33:32 +00:00
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.