NetBSD/tests
martin 4f7da0ce19 New gcc can reuse stack frames for tail calls, so "main" is an optional
frame as well.
2014-01-11 19:48:22 +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 Operation sysvbfs_remove() destructs inodes attached to active vnodes. 2014-01-09 13:23:57 +00:00
games
include fix unused variable warnings 2013-10-19 17:45:00 +00:00
ipf Mark two more test case as only failing for BE 2013-05-16 07:43:02 +00:00
kernel fix unused variable warnings 2013-10-19 17:45:00 +00:00
lib New gcc can reuse stack frames for tail calls, so "main" is an optional 2014-01-11 19:48:22 +00:00
libexec Disable integrated-assembler for clang on ARM for two files that are 2013-12-25 22:26:35 +00:00
modules Fix stupid thinko when checking for the availability of options MODULAR 2012-08-20 08:07:52 +00:00
net ldpd wants inet6 2014-01-03 13:14:50 +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 We now expect this test to succeed 2014-01-05 12:59:03 +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 Add some minimal tests of vmstat(1), to serve as regression tests 2014-01-07 16:47:13 +00:00
usr.sbin adjust output now that we don't output size info for links and directories 2013-10-20 17:27:37 +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
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

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.