NetBSD

History

ozaki-r 3f30ca4e9f Clean up clunky eval strings - Remove unnecessary \ at EOL - This allows to omit ; too - Remove unnecessary quotes for arguments of atf_set - Don't expand $DEBUG in eval - We expect it's expanded on execution Suggested by kre@		2017-08-03 03:16:26 +00:00
..
bin	PR bin/48498 PR bin/52426	2017-07-26 17:50:20 +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
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	Revert previous as it breaks at least sparc and hpcsh builds.	2017-07-25 21:26:56 +00:00
libexec	Avoid a race condition between dlclose and thread termination.	2017-07-21 16:39:20 +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	Clean up clunky eval strings	2017-08-03 03:16:26 +00:00
rump	Fix detection of expected results. The rump kernel code apparently	2017-05-03 12:09:41 +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	Do the previous test a better way - for a file, test is generally	2017-07-25 22:28:22 +00:00
usr.sbin	PR/51876: Ngie Cooper: kyua 0.11 $TMPDIR fixes	2017-01-14 20:45:16 +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

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.