NetBSD/tests
rillig b19a5288ba lint: add type information to 'possible pointer alignment problem [135]'
This warning occurs more than 7400 times in a regular NetBSD build, and
without giving any type information, leaves the reader clueless about
what the underlying issue might be.  Add type information since that is
a no-brainer to implement.
2021-02-28 00:40:22 +00:00
..
bin PR bin/55979 2021-02-16 09:46:24 +00:00
crypto
dev Unmount and unconfigure in the reverse order that they were done. Fixes 2021-01-14 04:30:40 +00:00
fs remove GCC_NO_ADDR_OF_PACKED_MEMBER for several subdir builds 2020-09-07 03:09:53 +00:00
games simplify: use two arguments again, suggested by kre@ 2020-10-11 18:43:50 +00:00
include
ipf
kernel Avoid hard-coding names and limits so this will not break again. 2020-10-31 14:57:02 +00:00
lib Adjust for conditional NLS 2021-02-25 22:37:36 +00:00
libexec Whitespace 2020-09-29 16:35:42 +00:00
modules
net Use a state of IPCP and IPv6CP to wait for connection established 2020-11-25 10:35:07 +00:00
rump for the busypage test, replace atf_tc_expect_fail() with atf_tc_skip() 2021-01-22 22:03:01 +00:00
sbin apply this change to a a couple more tests: 2020-12-10 08:16:59 +00:00
share Fix C++ file suffix (.cpp -> .cc) 2020-08-14 06:23:49 +00:00
sys Add tests for process_xmm_to_s87() and process_s87_to_xmm() 2020-10-15 17:44:44 +00:00
usr.bin lint: add type information to 'possible pointer alignment problem [135]' 2021-02-28 00:40:22 +00:00
usr.sbin Fix a few copy + pastos, simplify shell arithmetic 2020-08-14 05:22:25 +00:00
Makefile
Makefile.inc
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.