NetBSD/tests
2020-12-08 17:52:11 +00:00
..
bin Update the test a little so that is possible to pass 2020-10-30 22:03:35 +00:00
crypto
dev s/ we we / we / 2020-11-30 05:30:56 +00:00
fs
games simplify: use two arguments again, suggested by kre@ 2020-10-11 18:43:50 +00:00
include
ipf
kernel Avoid hard-coding names and limits so this will not break again. 2020-10-31 14:57:02 +00:00
lib map enough space for both the page we write and the guard so that we make 2020-11-27 16:50:02 +00:00
libexec Whitespace 2020-09-29 16:35:42 +00:00
modules
net Use a state of IPCP and IPv6CP to wait for connection established 2020-11-25 10:35:07 +00:00
rump the busypage test is buggy, expect it to fail. 2020-12-08 17:52:11 +00:00
sbin
share
sys Add tests for process_xmm_to_s87() and process_s87_to_xmm() 2020-10-15 17:44:44 +00:00
usr.bin Mark t_tsan_*:*profile test cases as expected failures as discussed in 2020-11-17 08:25:57 +00:00
usr.sbin
h_macros.h
Makefile
Makefile.inc
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.