NetBSD/tests
brad 01424baa92 The cleaner is compiled into the ATF test harness for the LFS
filesystem tests.  Use the new -J option to pass the raw device into
the cleaner.  This avoids the not rump safe getdiskrawname call and
makes sure we use an internal rump device name for cleaning.  This
should fix bin/54488.
2019-08-30 23:45:13 +00:00
..
bin Avoid symbol clashes in bin/df under MKSANITIZER 2019-08-15 08:24:11 +00:00
crypto The runtime of the ecdsa test case increased approximately sixfold 2019-06-16 10:45:50 +00:00
dev Gracefully skip test if not enough space in temporary directory. 2019-07-10 06:21:40 +00:00
fs The cleaner is compiled into the ATF test harness for the LFS 2019-08-30 23:45:13 +00:00
games
include Get rid of all the -lrumpdev and -lrumpvfs that are no longer needed 2019-05-13 17:55:07 +00:00
ipf
kernel Adapt tests/kernel/t_subr_prf for MKSANITIZER 2019-08-15 08:46:09 +00:00
lib Enhance the support of LLVM sanitizers 2019-08-27 22:48:53 +00:00
libexec return return atf_no_error() instead of 0 for consistency. 2019-07-09 16:24:01 +00:00
modules Drop no longer needed macros KCOV_STORE() KCOV_LOAD() in kcov(4) 2019-05-26 01:44:34 +00:00
net tests: add tests for IPv6 link-local addresses with a scope ID 2019-08-26 07:41:50 +00:00
rump Avoid symbol clashes in test/rump/modautoload/t_modautoload with sanitizers 2019-08-17 04:04:28 +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 issues with uvm_page_physunload_delete_end test case. 2019-01-16 13:54:17 +00:00
usr.bin Define target_not_supported_body() in TSan, MSan and libFuzzer tests 2019-08-23 06:39:54 +00:00
usr.sbin Get rid of all the -lrumpdev and -lrumpvfs that are no longer needed 2019-05-13 17:55:07 +00:00
Makefile
Makefile.inc
README
h_macros.h

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.