NetBSD/tests
andvar b58602814f fix typos in word "successful". 2021-09-16 22:19:10 +00:00
..
bin Add a new test case to check for correct parsing and execution 2021-09-09 00:04:51 +00:00
crypto
dev fix typos in word "successful". 2021-09-16 22:19:10 +00:00
fs fix typos in word "successful". 2021-09-16 22:19:10 +00:00
games
include
ipf
kernel
lib fix typos in word "successful". 2021-09-16 22:19:10 +00:00
libexec
modules
net fix various typos in comments and log messages. 2021-08-20 20:25:26 +00:00
rump
sbin fix typos in word "successful". 2021-09-16 22:19:10 +00:00
share
sys s/existant/existent/ in comments and messages, plus few more similar fixes. 2021-09-03 22:33:17 +00:00
usr.bin tests/lint: fix typo from previous commit 2021-09-14 19:08:40 +00:00
usr.sbin fix warnings 2021-09-01 06:12:50 +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.