NetBSD

History

kamil 7439bd598d Refactor lwp_create1 and lwp_exit1 into trace_thread* in ptrace(2) tests New tests: - trace_thread1 - trace_thread2 - trace_thread3 - trace_thread4 These tests verify _lwp_create(2) and _lwp_exit(2) events. They are currently skipped as not reliable.		2019-02-12 06:00:05 +00:00
..
bin
crypto
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	Refactor lwp_create1 and lwp_exit1 into trace_thread* in ptrace(2) tests	2019-02-12 06:00:05 +00:00
libexec
modules
net
rump
sbin
share
sys
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

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.