NetBSD

History

christos d8fc255716 Den't set SA_RESTART in the signal handler allowing the process to get interrupted durning recv and exit (pointed out by kre@)		2018-08-22 06:31:37 +00:00
..
bin	Several improvements to this test...	2018-07-20 18:25:56 +00:00
crypto	PR lib/53044: remove tests not provided by OpenSSL 1.1.x	2018-02-22 14:24:03 +00:00
dev	implement 32-bit compat support for raidframe.	2018-01-18 00:32:48 +00:00
fs	No semicolon after macro do ... while (0) wrapper.	2018-06-19 09:20:46 +00:00
games	Do this more cleanly - put the do-we-have-crypto check inside the actual	2016-06-27 05:29:32 +00:00
include	Avoid undefined behavior in an ATF test: t_bitops	2018-07-25 22:00:32 +00:00
ipf	Remove the "expected failure" from test n12, and change it not to use	2015-12-26 08:01:58 +00:00
kernel	Add a comment for the workaround in trigger_bus()	2018-05-30 17:48:13 +00:00
lib	Den't set SA_RESTART in the signal handler allowing the process to get	2018-08-22 06:31:37 +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	Update the error message in t_vlan (ENXIO => EINVAL)	2018-06-14 08:38:24 +00:00
rump	Fix build	2017-12-28 07:46:34 +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	When no gcc but clang can be found, fallback to the latter instead of	2016-03-12 08:55:54 +00:00
sys	Typos.	2018-02-08 09:05:16 +00:00
usr.bin	Disable profile and compat 32-bit c++ sanitizer tests	2018-07-16 07:27:26 +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.