NetBSD

History

isaki 6abe86a4fd Reduce the number of loops. It avoids timeout on slow machines, and I think that 100,000 times loop also satisfies the evaluation. PR lib/49664 (no comments)		2015-03-07 09:59:15 +00:00
..
bin	Visit the Bureau of Redundancy Department.	2014-09-11 18:25:30 +00:00
crypto	Sprinkle in some UNCONST()	2014-01-19 13:40:59 +00:00
dev	Double the timeout (to 120s) for slower machines	2015-02-27 09:16:07 +00:00
fs	one more MKZFS fix (how many subdirs does this place have?)	2015-01-08 04:00:31 +00:00
games
include	2 seconds is too small as timeout on slow machines, bump to 10 (my hppa	2015-02-27 08:30:30 +00:00
ipf	Null commit, to note that the previous commit by darrenr (which said	2014-12-06 19:31:25 +00:00
kernel	bump warns.	2015-01-14 22:22:32 +00:00
lib	Reduce the number of loops.	2015-03-07 09:59:15 +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	Bump timeout for a poll() call slightly, so the test has a chance to work	2015-02-27 13:15:49 +00:00
rump	call previous with the correct args too	2015-01-21 15:19:01 +00:00
sbin	Added test of -d option to sysctl	2014-05-16 18:50:28 +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	Make the dummy data that we expect to go into .data section bigger,	2015-02-17 11:51:04 +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	Run tests in kyua-atf-compat if MKKYUA!=no.	2013-02-25 00:33:19 +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.