Home | History | Annotate | only in /src/tests
Up to higher level directory
NameDateSize
bin/09-Nov-2022
compat/19-Aug-2023
crypto/09-Nov-2022
dev/Today
fs/Today
games/12-Oct-2024
h_macros.h20-Aug-20162.7K
include/01-Apr-2025
ipf/09-Nov-2022
kernel/Today
lib/Today
libexec/09-Nov-2022
Makefile19-Aug-2023746
Makefile.inc24-Apr-2023480
modules/08-Sep-2024
net/Today
README18-May-2012941
rump/09-Nov-2022
sbin/09-Nov-2022
share/09-Nov-2022
sys/Today
usr.bin/Today
usr.sbin/19-Oct-2024

README

      1 $NetBSD: README,v 1.4 2012/05/18 15:36:21 jruoho Exp $
      2 
      3 When adding new tests, please try to follow the following conventions.
      4 
      5 1. 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 
     13 2. 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 
     20 3. Otherwise use your own discretion.
     21