minix/tests
Ben Gras dda632a24f drop the minix_ prefixes for mmap and munmap
also cleanup of various minix-specific changes, cleanup of
mmap-related testing.

Change-Id: I289a4fc50cf8a13df4a6082038d860853a4bd024
2014-03-03 20:47:03 +01:00
..
bin Importing NetBSD "Kyua" test framework 2013-07-23 20:43:41 +02:00
crypto Importing NetBSD "Kyua" test framework 2013-07-23 20:43:41 +02:00
dev Importing NetBSD "Kyua" test framework 2013-07-23 20:43:41 +02:00
fs Importing NetBSD "Kyua" test framework 2013-07-23 20:43:41 +02:00
games Importing NetBSD "Kyua" test framework 2013-07-23 20:43:41 +02:00
include Importing NetBSD "Kyua" test framework 2013-07-23 20:43:41 +02:00
ipf Importing NetBSD "Kyua" test framework 2013-07-23 20:43:41 +02:00
kernel Importing NetBSD "Kyua" test framework 2013-07-23 20:43:41 +02:00
lib drop the minix_ prefixes for mmap and munmap 2014-03-03 20:47:03 +01:00
libexec Importing NetBSD "Kyua" test framework 2013-07-23 20:43:41 +02:00
modules Importing NetBSD "Kyua" test framework 2013-07-23 20:43:41 +02:00
net Importing NetBSD "Kyua" test framework 2013-07-23 20:43:41 +02:00
rump Importing NetBSD "Kyua" test framework 2013-07-23 20:43:41 +02:00
sbin Importing NetBSD "Kyua" test framework 2013-07-23 20:43:41 +02:00
share Importing NetBSD "Kyua" test framework 2013-07-23 20:43:41 +02:00
sys Importing NetBSD "Kyua" test framework 2013-07-23 20:43:41 +02:00
usr.bin Importing usr.bin/id 2013-11-12 10:15:47 -05:00
usr.sbin Importing NetBSD "Kyua" test framework 2013-07-23 20:43:41 +02:00
h_macros.h Importing NetBSD "Kyua" test framework 2013-07-23 20:43:41 +02:00
Makefile Importing NetBSD "Kyua" test framework 2013-07-23 20:43:41 +02:00
Makefile.inc fix a few more minix specific warnings 2013-08-27 16:16:03 +00:00
README Importing NetBSD "Kyua" test framework 2013-07-23 20:43:41 +02:00

$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.