NetBSD

History

ozaki-r 690df934db Add test cases for one SP with multiple SAs These are for a bug reported recently which modifies SPs accidentally.		2017-10-20 03:45:47 +00:00
..
bin	Add a new sub-test to validate ~ expansions.	2017-10-06 17:05:05 +00:00
crypto	constify more to avoid gcc stupidity.	2017-06-14 21:43:02 +00:00
dev	Remove MKCRYPTO option.	2017-05-21 15:28:36 +00:00
fs	give it more time.	2017-05-24 15:29:51 +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	Remove the "expected failure" from test n12, and change it not to use	2015-12-26 08:01:58 +00:00
kernel	Stress rump hyperentropy a little harder.	2017-04-16 18:24:23 +00:00
lib	add test case for new format 'f' and 'F'	2017-10-14 18:41:44 +00:00
libexec	Add sparc/sparc64 support for irelative relocations.	2017-08-12 09:03:27 +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	Add test cases for one SP with multiple SAs	2017-10-20 03:45:47 +00:00
rump	Add declaration. build fix	2017-09-29 13:19:57 +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
h_macros.h	provide an RL variant that prints an extra argument	2016-08-20 15:49:08 +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	Clarify this a little.	2012-05-18 15:36:21 +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.