NetBSD

History

ozaki-r 11f91074e6 Change the prefix of test names to ipsecif_ to distinguish from tests for ipsec(4)		2018-01-11 07:58:22 +00:00
..
bin	Add a test case for "set -X".	2017-11-16 19:41:41 +00:00
crypto	constify more to avoid gcc stupidity.	2017-06-14 21:43:02 +00:00
dev	Fix fallout from hid factorisation:	2017-12-10 20:38:13 +00:00
fs	ATF test program for PR kern/52738: check for mtime updates after rewriting	2017-11-19 21:05:26 +00:00
games	Do this more cleanly - put the do-we-have-crypto check inside the actual	2016-06-27 05:29:32 +00:00
include	Update recently-added test to adapt to new signature of LIST_MOVE()	2017-10-02 05:14:29 +00:00
ipf	…
kernel	Add EVFILT_FS	2018-01-09 17:35:29 +00:00
lib	Implement helper function for alpha	2017-12-30 16:35:03 +00:00
libexec	Build less of the test code if there's no linker ifunc support.	2018-01-01 06:34:13 +00:00
modules	Skip the test on non-modular kernels	2018-01-09 15:16:02 +00:00
net	Change the prefix of test names to ipsecif_ to distinguish from tests for ipsec(4)	2018-01-11 07:58:22 +00:00
rump	Fix build	2017-12-28 07:46:34 +00:00
sbin	Make most of the resize_ffs tests skip if PUFFS is not configured	2017-10-08 21:12:27 +00:00
share	When no gcc but clang can be found, fallback to the latter instead of	2016-03-12 08:55:54 +00:00
sys	convention about function names for predicate checking:	2016-12-22 08:15:20 +00:00
usr.bin	Do the previous test a better way - for a file, test is generally	2017-07-25 22:28:22 +00:00
usr.sbin	Add test mtree -O with same hash value in directory and leaf.	2017-09-07 04:05:21 +00:00
Makefile	Remove MKCRYPTO option.	2017-05-21 15:28:36 +00:00
Makefile.inc	better name	2017-01-14 01:33:32 +00:00
README	…
h_macros.h	provide an RL variant that prints an extra argument	2016-08-20 15:49:08 +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.