• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..--

atf/20-Jan-2014-

bin/16-Jan-2021-14,37910,474

crypto/20-Jan-2014-5,1243,508

dev/21-Oct-2017-17,49113,859

examples/20-Jan-2014-

fs/31-Dec-2022-17,88212,016

games/07-Feb-2025-309214

include/06-May-2025-6,3644,965

ipf/21-Dec-2021-18,12416,289

kernel/06-May-2025-13,6058,712

lib/07-Feb-2025-340,766298,363

libexec/06-Sep-2014-2,9501,834

modules/07-Feb-2025-3,9882,789

net/07-Feb-2025-14,99910,067

rump/27-May-2016-4,3352,680

sbin/16-Jan-2021-3,3071,996

share/20-Jan-2014-593354

sys/16-Jan-2021-400243

syscall/20-Jan-2014-

toolchain/20-Jan-2014-

usr.bin/07-Feb-2025-54,06233,809

usr.sbin/07-Feb-2025-1,098772

util/20-Jan-2014-

MakefileD07-Feb-2025746 4428

Makefile.incD07-Feb-2025480 1512

READMED18-May-2012941 2115

h_macros.hD21-Oct-20172.7 KiB8847

README

1$NetBSD: README,v 1.4 2012/05/18 15:36:21 jruoho 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