NetBSD

History

jakllsch c38078a218 locate_item() doesn't need to have a flags argument, as the flags are also in the hid item data structure.		2016-01-09 14:31:19 +00:00
..
bin	more robust ulimit test that works with most variants of bourne shells.	2015-12-30 22:24:44 +00:00
crypto	For the skipped ARC4 test, don't bother trying to run the test clean-up	2015-12-26 07:10:03 +00:00
dev	locate_item() doesn't need to have a flags argument, as the flags	2016-01-09 14:31:19 +00:00
fs	create_many:	2016-01-02 12:11:30 +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	Remove the "expected failure" from test n12, and change it not to use	2015-12-26 08:01:58 +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	Don't crash when the device's HID Report Descriptor Pops from an empty stack.	2016-01-07 16:10:49 +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	Add some tests for sysctl net.inet.ip.*	2015-12-25 08:22:28 +00:00
rump	Remove a left-over debugging variable. Fix the build.	2015-12-27 08:21:44 +00:00
sbin	I was right - the output from gpt(8) did grow an extra space character!	2015-12-27 06:53:48 +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	Add an anonymous struct test	2015-10-14 16:32:55 +00:00
usr.sbin	t_tcpdump: skip bridges	2014-09-20 06:08:07 +00:00
h_macros.h	cast and mask is overkill.	2015-01-14 22:57:27 +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	Do not care about dead functions for test cases, in this case it is	2011-09-16 16:30:18 +00:00
README	Clarify this a little.	2012-05-18 15:36:21 +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.