NameDateSize

..07-May-202431

bin/H03-Jul-202015

compat/H21-Aug-20235

crypto/H12-Oct-20157

dev/H07-May-202415

fs/H06-Jun-202224

games/H29-Apr-20245

h_macros.hH A D22-Dec-20162.7 KiB

include/H05-Aug-202321

ipf/H11-Nov-202116

kernel/H07-May-202450

lib/H07-May-202436

libexec/H12-Oct-20156

MakefileH A D21-Aug-2023746

Makefile.incH A D25-Apr-2023480

modules/H29-Apr-202421

net/H07-May-202440

READMEH A D18-May-2012938

rump/H22-Dec-201610

sbin/H26-Jun-202015

share/H12-Oct-20156

sys/H07-May-202412

usr.bin/H07-May-202456

usr.sbin/H27-Aug-202315

README

1$NetBSD: README,v 1.3 2012/02/13 08:55:20 wiz Exp $
2
3When adding new tests, please try to follow the following conventions.
4
51. For library routines, including system calls, the directory structure of
6   the tests should follow the directory structure of the real source tree.
7   For instance, interfaces available via the C library should follow:
8
9	src/lib/libc/gen -> src/tests/lib/libc/gen
10	src/lib/libc/sys -> src/tests/lib/libc/sys
11	...
12
132. Equivalently, all tests for userland utilities should try to follow their
14   location in the source tree. If this can not be satisfied, the tests for
15   a utility should be located under the directory to which the utility is
16   installed. Thus, a test for env(1) should go to src/tests/usr.bin/env.
17   Likewise, a test for tcpdump(8) should be in src/tests/usr.sbin/tcpdump,
18   even though the source code for the program is located under src/external.
19
203. Otherwise use your own discretion.
21