NetBSD/tests
reinoud f3954b9d18 Cover the last failing UDF test cases with a reference to PR kern/47986, i.e.
all rename's fail until UDF switches over to the new rename framework solving
the locking mechanism.
2013-07-08 06:44:51 +00:00
..
bin New testcase to check limits flags for ulimit builtin. 2012-06-11 18:32:59 +00:00
crypto more MKCRYPTO_IDEA and MKCRYPTO_MDC2 removal (resp, adjustment to IDEA and 2012-07-14 16:04:04 +00:00
dev The sh api calls it atf_expect_fail, while the c api calls it 2013-04-14 16:07:46 +00:00
fs Cover the last failing UDF test cases with a reference to PR kern/47986, i.e. 2013-07-08 06:44:51 +00:00
games
include use __BITMAP_TYPE 2012-12-07 02:28:19 +00:00
ipf Mark two more test case as only failing for BE 2013-05-16 07:43:02 +00:00
kernel Don't rely on "kill -0" to check whether a background shell command 2013-05-31 14:40:48 +00:00
lib Put the vfork at the end. 2013-07-05 09:55:39 +00:00
libexec
modules Fix stupid thinko when checking for the availability of options MODULAR 2012-08-20 08:07:52 +00:00
net Remove makevirtif(), it's not likely to be used in testing. 2013-07-03 19:13:33 +00:00
rump
sbin Check for RUMP programs before using them. 2013-02-19 21:08:24 +00:00
share Hook Lutok into the build. This is all protected by the MKKYUA guard. 2013-02-16 21:40:05 +00:00
sys
usr.bin PR/47825: Garrett Cooper: Fix hardcoding of NetBSD in t_grep.sh 2013-05-17 15:39:17 +00:00
usr.sbin Check for RUMP programs before using them. 2013-02-19 21:08:24 +00:00
h_macros.h PR/47826: Garrett Cooper: Add <sys/types.h>. Really I am tempted to remove 2013-05-17 15:42:09 +00:00
Makefile Run tests in kyua-atf-compat if MKKYUA!=no. 2013-02-25 00:33:19 +00:00
Makefile.inc
README Clarify this a little. 2012-05-18 15:36:21 +00:00

$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.