NetBSD/tests
thorpej 032c1d01a1 Add a test case that exercises repeated sceduling and cancelling of a job,
with periodic dropping of the interlock.
2018-12-28 19:54:36 +00:00
..
bin Add a new test case for NetBSD specific readonly tests. 2018-12-12 11:52:05 +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 Have to hijack sysctl() and modctl() for zfs commands. 2018-12-16 14:04:14 +00:00
games
include Avoid undefined behavior in an ATF test: t_bitops 2018-07-25 22:00:32 +00:00
ipf
kernel kre@ notified me that the kernel/t_threadpool "rapid" test was occasionally 2018-12-28 16:01:53 +00:00
lib Add an initfini_array test that does not depend on the linker putting it 2018-12-27 19:33:52 +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 ipsecif(4) which connect to two peers in the same NAPT. 2018-12-26 08:59:41 +00:00
rump Add a test case that exercises repeated sceduling and cancelling of a job, 2018-12-28 19:54:36 +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
sys Fixed the build failures caused by incompatible type comparisons. 2018-12-18 07:11:35 +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
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
h_macros.h provide an RL variant that prints an extra argument 2016-08-20 15:49:08 +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.