NetBSD/tests
martin d7363146ee Pull up following revision(s) (requested by riastradh in ticket #1601):
tests/lib/libc/string/t_swab.c: revision 1.3
	lib/libc/string/swab.c: revision 1.20

swab(3): Rewrite this to be understandable.

And make the tests work, and exercise all lengths up to 100.
Evidently the previous definition, presumably tightly optimized for
1980s-era compilers and CPUs, was too hard to understand, because it
was incorrectly tested for two decades and broken for years.

PR lib/57141
2023-02-22 18:49:17 +00:00
..
bin Pull up following revision(s) (requested by kamil in ticket #65): 2019-08-16 19:18:07 +00:00
crypto The runtime of the ecdsa test case increased approximately sixfold 2019-06-16 10:45:50 +00:00
dev Gracefully skip test if not enough space in temporary directory. 2019-07-10 06:21:40 +00:00
fs Pull up following revision(s) (requested by riastradh in ticket #1083): 2020-09-13 12:25:29 +00:00
games
include
ipf
kernel Pull up following revision(s) (requested by thorpej in ticket #1353): 2021-10-04 14:48:25 +00:00
lib Pull up following revision(s) (requested by riastradh in ticket #1601): 2023-02-22 18:49:17 +00:00
libexec return return atf_no_error() instead of 0 for consistency. 2019-07-09 16:24:01 +00:00
modules
net Pull up following revision(s) (requested by knakahara in ticket #1129): 2020-11-10 11:44:22 +00:00
rump Pull up following revision(s) - all via patch - 2021-07-06 04:22:34 +00:00
sbin
share
sys
usr.bin Pull up following revision(s) (requested by kamil in ticket #120): 2019-08-29 16:45:25 +00:00
usr.sbin
Makefile
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.