NetBSD/tests
2013-10-12 17:26:32 +00:00
..
bin Fix PR bin/48202 [non-critical/low]: 2013-10-06 21:05:50 +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 Remove what looks like an outdated assert (there was something very sneaky 2013-09-09 19:47:38 +00:00
games Since /usr/games is rarely in one's $PATH, provide an absolute path to the 2010-11-19 12:31:36 +00:00
include socket(-1, SOCK_CLOEXEC, 0); followed by the process exiting (i.e. 2013-09-05 12:22:10 +00:00
ipf Mark two more test case as only failing for BE 2013-05-16 07:43:02 +00:00
kernel Fix msgsz confusion. 2013-07-24 11:44:10 +00:00
lib Retry previous 2013-09-16 15:33:24 +00:00
libexec Introduce __HAVE_NO___THREAD for sun2 and vax to disable the TLS usage. 2012-01-17 20:34:57 +00:00
modules Fix stupid thinko when checking for the availability of options MODULAR 2012-08-20 08:07:52 +00:00
net more tests 2013-10-12 17:26:32 +00:00
rump Use 8 TCP/IP stacks instead of 16. That still gives us plenty crossping 2013-09-09 19:27:49 +00:00
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 Adjusts tests after import of atf-0.12: 2010-11-07 17:51:16 +00:00
usr.bin Add some cases pertaining to another bug I just fixed. 2013-08-11 01:50:02 +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 Do not care about dead functions for test cases, in this case it is 2011-09-16 16:30:18 +00:00
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.