NetBSD/tests
rillig ca061b3a21 lint: fix wrong error in strict bool mode in condition with comma
For the result of the comma operator, it doesn't matter whether the
comma itself comes from a system header or not.  Instead, it's the main
operator of the right operand.

Since 2021-11-16.
2021-12-22 15:36:37 +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 s/shapshot/snapshot/ 2021-12-05 07:51:26 +00:00
games
include
ipf s/endianess/endianness/ 2021-11-10 17:19:29 +00:00
kernel tests/t_magic_symlinks: remove duplicate word in test description 2021-12-09 06:38:23 +00:00
lib When running the tests under "qemu -accel kvm" on a Linux host, 2021-12-15 09:19:28 +00:00
libexec
modules
net s/encript/encrypt/ in comment. 2021-12-05 02:49:21 +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
sys s/existant/existent/ in comments and messages, plus few more similar fixes. 2021-09-03 22:33:17 +00:00
usr.bin lint: fix wrong error in strict bool mode in condition with comma 2021-12-22 15:36:37 +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.