NetBSD/tests
christos b6bcbcb52f more tests from kamil 2016-10-31 23:51:20 +00:00
..
bin PR bin/4841 was filed regarding the handling of blank lines when cat was invoked 2016-06-26 22:50:46 +00:00
crypto periphereal updates and generated files for the new openssl. 2016-10-14 16:09:43 +00:00
dev pad(4) must be open before corresponding audio device is opened. 2016-10-15 07:08:06 +00:00
fs Incrase timeout for the benefit of the walk_list_user test case which 2016-10-08 13:23:53 +00:00
games Do this more cleanly - put the do-we-have-crypto check inside the actual 2016-06-27 05:29:32 +00:00
include We now need librumpdev to resolve rumpns_config_cfdriver_attach which 2016-08-08 14:11:08 +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 Test for PR kern/51135 is no longer failing. 2016-05-22 04:34:44 +00:00
lib more tests from kamil 2016-10-31 23:51:20 +00:00
libexec Really revert to the original version. 2014-08-26 17:13:42 +00:00
modules Define _KERNTYPES for things that need it. 2016-01-23 21:22:45 +00:00
net Add tests for ping6 options 2016-10-31 10:38:25 +00:00
rump Disable aslr too since we are playing address space range tricks. 2016-10-14 16:02:35 +00:00
sbin When deadbeef is treated as a 32-bit signed integer, it actually has a 2016-06-17 03:55:35 +00:00
share When no gcc but clang can be found, fallback to the latter instead of 2016-03-12 08:55:54 +00:00
sys catch up with link printing. 2016-08-27 11:30:49 +00:00
usr.bin Add tests for uniq(1) based on the example test cases provided in the POSIX man page. 2016-10-22 14:13:39 +00:00
usr.sbin + -lrumpdev 2016-08-10 23:07:57 +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 provide an RL variant that prints an extra argument 2016-08-20 15:49:08 +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.