NetBSD/tests
2018-11-28 09:58:58 +00:00
..
bin Add two new test cases to add more tests for $@ expansions 2018-11-27 09:59:30 +00:00
crypto A timeout of 480 seconds is not enough for the t_pubkey:ec test case 2018-09-29 10:54:35 +00:00
dev implement 32-bit compat support for raidframe. 2018-01-18 00:32:48 +00:00
fs Add missing access check for REMOVE into zfs_netbsd_lookup(). 2018-11-28 09:58:58 +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 Avoid undefined behavior in an ATF test: t_bitops 2018-07-25 22:00:32 +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 Make fenv.h optional for this test to unbreak the vax build. 2018-11-12 05:02:00 +00:00
lib cbrtl_powl is xfail only if long double has more bits than double. 2018-11-15 05:14:20 +00:00
libexec Avoid casting fun by switching ifunc helper functions to return 2018-03-09 20:15:03 +00:00
modules Skip the test on non-modular kernels 2018-01-09 15:16:02 +00:00
net Add ATF for IPv6 NAT-T. 2018-11-22 04:51:41 +00:00
rump Fix build 2017-12-28 07:46:34 +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 Typos. 2018-02-08 09:05:16 +00:00
usr.bin Move the tests of character value args to floating conversions 2018-09-14 19:57:57 +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

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