NetBSD/tests
knakahara d1268e2e86 Add ATF for IPv6 NAT-T.
We use IPv6 NAT-T to avoid IPsec slowing down caused by dropping ESP packets
by some Customer Premises Equipments (CPE). I implement ATF to test such
situation.

I think it can also work with nat66, but I have not tested to the fine details.
2018-11-22 04:51:41 +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
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
net Add ATF for IPv6 NAT-T. 2018-11-22 04:51:41 +00:00
rump
sbin
share
sys
usr.bin Move the tests of character value args to floating conversions 2018-09-14 19:57: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.