NetBSD/tests
andvar b433853d68 s/rouding/rounding/ in test description. 2024-01-14 12:44:09 +00:00
..
bin s/synax/syntax/ in test description. 2023-12-28 20:04:10 +00:00
compat tests/compat/linux: fix typo in comment 2023-08-23 20:05:05 +00:00
crypto Remove PROGDPLIBSSTATIC from ec and threads; dh still needs it because it 2023-08-22 17:27:48 +00:00
dev mmap() fails for size == 0 with EINVAL unless the mapping is anonymous. 2023-12-11 09:26:08 +00:00
fs PR 57803: fix typo in test title. 2023-12-30 13:09:24 +00:00
games
include tests/include/t_paths: Test all paths, nonfatally. 2023-08-05 12:11:05 +00:00
ipf
kernel tests: Audit RZ abuse. 2023-11-24 17:31:03 +00:00
lib s/rouding/rounding/ in test description. 2024-01-14 12:44:09 +00:00
libexec t_dlinfo, t_rtld_r_debug: Audit ATF_REQUIRE/CHECK, sprinkle messages. 2023-11-24 17:40:20 +00:00
modules
net Added the test for vlan over l2tp 2023-11-02 09:50:50 +00:00
rump workqueue(9) tests: Fix mistake in rev. 1.9. 2023-08-10 22:20:20 +00:00
sbin ifconfig/t_capabilities: s/if_capabilities/if_capenable/ in message 2023-10-18 08:52:46 +00:00
share
sys apply previous to just GCC. 2023-09-05 22:14:08 +00:00
usr.bin lint: warn about integer overflow when folding constant INT_MIN / -1 2024-01-11 20:25:04 +00:00
usr.sbin remove dup copy. 2023-12-02 16:18:17 +00:00
Makefile Tests for the compat_linux inotify framework from GSoC 2023 (Theodore Preduta) 2023-08-19 22:56:43 +00:00
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.