NetBSD/tests
blymn f596e5447e Add the -F flag to the getopt string, it was there in the help and
in the arguments handling but getopt was not told about it.
2022-03-01 06:41:27 +00:00
..
bin PR bin/53550 2021-11-22 05:21:54 +00:00
crypto s/rouine/routine/ 2021-12-05 07:33:56 +00:00
dev s/occured/occurred/ in comments, log messages and man pages. 2021-12-10 20:36:02 +00:00
fs Test mkdir(2) with one or more trailing slashes - this currently fails 2022-02-01 18:27:24 +00:00
games simplify: use two arguments again, suggested by kre@ 2020-10-11 18:43:50 +00:00
include Mask NULL + 0 LLVM UBSan reports in the ATF test: t_pslist.c 2020-05-31 16:36:07 +00:00
ipf s/endianess/endianness/ 2021-11-10 17:19:29 +00:00
kernel remove double t from targeted, add missing r to arbitrary 2022-01-26 11:48:53 +00:00
lib Add the -F flag to the getopt string, it was there in the help and 2022-03-01 06:41:27 +00:00
libexec Trailing whitespace 2022-01-14 07:34:07 +00:00
modules KMODULEDIR is no longer absolute (${DESTDIR} is added to it by the system 2020-05-01 22:24:18 +00:00
net s/udpate/update/ 2022-01-07 22:59:32 +00:00
rump Allow to set sanitizer flags for the rump build from the 2021-07-07 11:51:45 +00:00
sbin Delete trailing whitespace 2021-10-30 13:50:12 +00:00
share Fix C++ file suffix (.cpp -> .cc) 2020-08-14 06:23:49 +00:00
sys Mark randomly failing test cases as expected failures with a reference 2022-02-26 16:21:59 +00:00
usr.bin tests/lint: add tests for messages about old-style functions 2022-02-27 20:02:43 +00:00
usr.sbin fix warnings 2021-09-01 06:12:50 +00:00
Makefile
Makefile.inc Allow to set sanitizer flags for the rump build from the 2021-07-07 11:51:45 +00:00
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.