NetBSD/tests
ozaki-r c656a96f13 Improve test stability
ifconfig -a -v after ifconfig -a -z is expected to show '0 packets' for
all interface. However, shmif0 can receive packets between the two
operations. So we have to keep shmif0 down during such tests.
2015-09-15 09:51:01 +00:00
..
bin another wait test. 2015-08-23 07:15:16 +00:00
crypto correct test name 2015-03-16 16:42:27 +00:00
dev Don't build tests that depend on RUMP if BSD_MK_COMPAT_FILE is defined. 2015-06-22 00:05:23 +00:00
fs Remove rubbish. 2015-08-30 18:27:26 +00:00
games
include Don't build tests that depend on RUMP if BSD_MK_COMPAT_FILE is defined. 2015-06-22 00:05:23 +00:00
ipf Null commit, to note that the previous commit by darrenr (which said 2014-12-06 19:31:25 +00:00
kernel Don't build tests that depend on RUMP if BSD_MK_COMPAT_FILE is defined. 2015-06-22 00:05:23 +00:00
lib make error more informative. 2015-09-12 15:21:33 +00:00
libexec Really revert to the original version. 2014-08-26 17:13:42 +00:00
modules Fix static linking for the tests: -lrump is also used by -lrumpuser, 2014-06-10 04:28:39 +00:00
net Improve test stability 2015-09-15 09:51:01 +00:00
rump call previous with the correct args too 2015-01-21 15:19:01 +00:00
sbin - Add new tests for -c check flag in resize_ffs 2015-03-29 19:37:02 +00:00
share Hook Lutok into the build. This is all protected by the MKKYUA guard. 2013-02-16 21:40:05 +00:00
sys Add casts for big endian machines 2014-12-03 13:10:49 +00:00
usr.bin new test 2015-07-29 18:26:15 +00:00
usr.sbin t_tcpdump: skip bridges 2014-09-20 06:08:07 +00:00
Makefile Don't build tests that depend on RUMP if BSD_MK_COMPAT_FILE is defined. 2015-06-22 00:05:23 +00:00
Makefile.inc
README
h_macros.h cast and mask is overkill. 2015-01-14 22:57:27 +00:00

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.