NetBSD

History

christos 272d6823df fix clang build.		2016-12-17 03:43:38 +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	Update test output to reflect audio changes.	2016-12-11 08:09:29 +00:00
fs	- Change vcache_reclaim() to always call VOP_INACTIVE() before VOP_RECLAIM().	2016-12-01 14:49:03 +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	fix clang build.	2016-12-17 03:43:38 +00:00
lib	sig_atomic_t does not include volatile. Prevent static analysis from	2016-12-12 10:34:55 +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 multiple routers	2016-12-16 09:11:18 +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
h_macros.h	provide an RL variant that prints an extra argument	2016-08-20 15:49:08 +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

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.