NetBSD/tests
rillig 87f7a17b45 lint: do not warn about pointer casts to array types
If the (recursive) element type of the array is compatible, that's good
enough.  Even after the previous commits, this warning is the one that
occurs most in a standard NetBSD build, and it is generally ignored.
For now, focus on reducing the number of false positives to an
acceptable level.
2022-06-24 21:22:11 +00:00
..
bin tests/dd: add more test cases for swapping bytes 2022-05-24 21:42:37 +00:00
crypto PR 56875: Bump timeout for the bignumber test to 2h, as suggested 2022-06-10 05:59:12 +00:00
dev fix various typos in comments, documentation and messages. 2022-05-31 08:43:13 +00:00
fs build system: Revert all the recent additions of MK[...] knobs that 2022-06-06 10:56:27 +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 fix various typos in comment, documentation and log messages. 2022-05-24 20:50:17 +00:00
lib test: fix typo and improve wording 2022-06-22 21:11:41 +00:00
libexec sort; it is the same list as in h_ifunc_static.c; perhaps it should be 2022-06-21 16:24:37 +00:00
modules
net PR 56879: bump timeout for the wg_malformed test to 100 seconds, 2022-06-13 07:59:15 +00:00
rump fix various typos in comments, docs and log messages. 2022-05-24 06:27:59 +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 lint: do not warn about pointer casts to array types 2022-06-24 21:22:11 +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.