NetBSD/tests
2019-03-22 01:50:14 +00:00
..
bin Add sub tests to the quoting test case, to demonstrate a parsing 2019-01-22 14:31:53 +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 use strncpy() into a buffer that may not be nul terminated. 2019-02-06 09:16:49 +00:00
fs s/ are are / are / 2019-03-08 08:35:58 +00:00
games
include - add or adjust /* FALLTHROUGH */ where appropriate 2019-02-03 03:19:25 +00:00
ipf
kernel Fix reporting EOF via kevent and add a test case 2019-02-15 18:57:15 +00:00
lib Fix build break due to typos. 2019-03-22 01:50:14 +00:00
libexec Avoid casting fun by switching ifunc helper functions to return 2018-03-09 20:15:03 +00:00
modules Introduce enhancements to the kcov(4) code 2019-03-10 22:34:14 +00:00
net Add ATF for ipsecif(4) pfil. 2019-01-17 02:49:11 +00:00
rump Fix a silly bug the "cancel thrash" test: the exit condition for the 2019-01-04 05:35:24 +00:00
sbin
share
sys Fixed issues with uvm_page_physunload_delete_end test case. 2019-01-16 13:54:17 +00:00
usr.bin fix hello_profile's hello_profile_head function name. 2019-02-09 02:36:28 +00:00
usr.sbin
h_macros.h
Makefile
Makefile.inc
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.