NetBSD

History

ozaki-r 7dd2779b49 Reflect a fix for bridge Due to PR 48104, some tests of ping/ping6 were failed but the tests now should be successful. So reverse atf_check. Bonus: the fix for PR 48104 also fixes another uknown failure.		2015-07-23 11:05:34 +00:00
..
bin	Visit the Bureau of Redundancy Department.	2014-09-11 18:25:30 +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	Apparently I fixed t_unpriv:zfs_owner and didn't notice.	2015-04-09 19:51:13 +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	Build t_fpgetmask/t_fpgetround for aarch64 since they are now in libc	2015-07-08 01:09:25 +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	Reflect a fix for bridge	2015-07-23 11:05:34 +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-01 15:36:44 +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	Clarify this a little.	2012-05-18 15:36:21 +00:00
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.