NetBSD

History

kre a94bbc243b Make sure that the open of /dev/pad0 has succeeded (or at the very least been attempted) before attempting to open /dev/mixer to determine if the system being tested has audio or not. Leaving this for the background cat command to do causes a race between that command and the parent sh. Move this code to a helper function to avoid duplicating it. Also avoid attempting to kill the background cat if it was never created. The kill is likely unnecessary anyway, ATF seems to clean up processes like that one without assistance. Which is a good thing, as the kill does not happen if the test is skipped, or fails.		2017-07-18 12:40:57 +00:00
..
bin	Add some tests for the (likely forthcoming) pipefail option (modelled	2017-07-15 18:52:21 +00:00
crypto	constify more to avoid gcc stupidity.	2017-06-14 21:43:02 +00:00
dev	Remove MKCRYPTO option.	2017-05-21 15:28:36 +00:00
fs	give it more time.	2017-05-24 15:29:51 +00:00
games
include
ipf
kernel
lib	Add a simple collation test. This test is expected to fail on HEAD since	2017-07-14 14:57:43 +00:00
libexec	Implement __cxa_thread_atexit and __cxa_thread_atexit_impl. This	2017-07-11 15:21:31 +00:00
modules
net	Separate test files	2017-07-18 02:16:07 +00:00
rump
sbin
share
sys
usr.bin	Make sure that the open of /dev/pad0 has succeeded (or at the very	2017-07-18 12:40:57 +00:00
usr.sbin
h_macros.h
Makefile	Remove MKCRYPTO option.	2017-05-21 15:28:36 +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.