NetBSD

History

kre fa836fad8c It turns out there are more cases where escaping of meta-chars was not being done properly (too many different code paths inside sh) so add even more subtests to the case_matching test case to verify that all (that I can think of for now anyway) get fixed when this gets cleaned up. The case_matching test case still fails, but now 6 of its subtests should fail (until sh is corrected ... soon).		2018-11-18 13:41:24 +00:00
..
bin	It turns out there are more cases where escaping of meta-chars	2018-11-18 13:41:24 +00:00
crypto	A timeout of 480 seconds is not enough for the t_pubkey:ec test case	2018-09-29 10:54:35 +00:00
dev	implement 32-bit compat support for raidframe.	2018-01-18 00:32:48 +00:00
fs	No semicolon after macro do ... while (0) wrapper.	2018-06-19 09:20:46 +00:00
games	…
include	Avoid undefined behavior in an ATF test: t_bitops	2018-07-25 22:00:32 +00:00
ipf	…
kernel	Make fenv.h optional for this test to unbreak the vax build.	2018-11-12 05:02:00 +00:00
lib	cbrtl_powl is xfail only if long double has more bits than double.	2018-11-15 05:14:20 +00:00
libexec	Avoid casting fun by switching ifunc helper functions to return	2018-03-09 20:15:03 +00:00
modules	Skip the test on non-modular kernels	2018-01-09 15:16:02 +00:00
net	let ATF detect a bug fixed by if_vla.c:r1.132.	2018-11-14 05:07:48 +00:00
rump	Fix build	2017-12-28 07:46:34 +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	Typos.	2018-02-08 09:05:16 +00:00
usr.bin	Move the tests of character value args to floating conversions	2018-09-14 19:57:57 +00:00
usr.sbin	Add test mtree -O with same hash value in directory and leaf.	2017-09-07 04:05:21 +00:00
Makefile	Remove MKCRYPTO option.	2017-05-21 15:28:36 +00:00
Makefile.inc	…
README	…
h_macros.h	…

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.