NetBSD/tests
kamil 5a04cbf366 Link t_ptrace_wait* tests with -pthread
While there, bump (c) for ATF ptrace(2) tests.

Add __used in infinite_thread() for consistency with other functions in
the file.
2019-02-10 02:13:45 +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 don't check the return value of execvp() for failure to call err(). 2019-02-01 09:06:07 +00:00
games
include - add or adjust /* FALLTHROUGH */ where appropriate 2019-02-03 03:19:25 +00:00
ipf
kernel - tests explicitly check failure modes, ignore those warnings 2019-02-04 05:24:18 +00:00
lib Link t_ptrace_wait* tests with -pthread 2019-02-10 02:13:45 +00:00
libexec Avoid casting fun by switching ifunc helper functions to return 2018-03-09 20:15:03 +00:00
modules Merge the [pgoyette-compat] branch 2019-01-27 02:08:33 +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 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 fix hello_profile's hello_profile_head function name. 2019-02-09 02:36:28 +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
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.