NetBSD/tests
pgoyette ea561c44e3 Update the t_modctl test to ensure that static evcnts are added.
While here, remove the explicit call to sysctl_setup() routine,
since the module infrastructure already invokes such routines
automatically.
2020-02-22 19:54:34 +00:00
..
bin Avoid symbol clashes in bin/df under MKSANITIZER 2019-08-15 08:24:11 +00:00
crypto Add HMAC-SHA-{256,384,512} test cases. 2019-12-03 04:20:45 +00:00
dev Update AUDIO_SETINFO_channels test. 2020-02-22 05:53:19 +00:00
fs introduce some common variables for use in GCC warning disables: 2019-10-13 07:28:04 +00:00
games
include Adapt <sys/pslist.h> to use atomic_load/store_*. 2019-12-01 15:28:19 +00:00
ipf
kernel Test that fpu state is preserved by fork. 2020-02-11 03:15:10 +00:00
lib Disable t_ptrace_wait* tests for MKSANITIZER/MKLIBCSANITIZER 2020-02-22 19:44:07 +00:00
libexec return return atf_no_error() instead of 0 for consistency. 2019-07-09 16:24:01 +00:00
modules Update the t_modctl test to ensure that static evcnts are added. 2020-02-22 19:54:34 +00:00
net tests: abort if MAC address duplication found 2020-02-20 08:02:26 +00:00
rump Hopefully fix some problems seen with MP support on non-x86, in particular 2020-01-08 17:38:41 +00:00
sbin Make most of the resize_ffs tests skip if PUFFS is not configured 2017-10-08 21:12:27 +00:00
share
sys Fixed issues with uvm_page_physunload_delete_end test case. 2019-01-16 13:54:17 +00:00
usr.bin Mark compilation with -pg as xfail on aarch64. 2020-02-11 06:26:19 +00:00
usr.sbin Get rid of all the -lrumpdev and -lrumpvfs that are no longer needed 2019-05-13 17:55:07 +00:00
h_macros.h
Makefile Remove MKCRYPTO option. 2017-05-21 15:28:36 +00:00
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.