NetBSD

History

blymn a90239df44 Uncomment the waddstr call that was returning ERR, this is actually correct so make the expected return ERR then repeat the call with scrollok set to true to validate. Do refreshes on the window instead of stdscr so we get the window contents reported and update the check files with the expected output.		2022-11-10 06:13:29 +00:00
..
bin	tests/dd: add more test cases for swapping bytes	2022-05-24 21:42:37 +00:00
crypto	PR 56875: Bump timeout for the bignumber test to 2h, as suggested	2022-06-10 05:59:12 +00:00
dev	When run from py-anita/amd64 this test fails with:	2022-08-13 17:46:26 +00:00
fs	build system: Revert all the recent additions of MK[...] knobs that	2022-06-06 10:56:27 +00:00
games	…
include	…
ipf	…
kernel	fix various typos in comment, documentation and log messages.	2022-05-24 20:50:17 +00:00
lib	Uncomment the waddstr call that was returning ERR, this is actually	2022-11-10 06:13:29 +00:00
libexec	sort; it is the same list as in h_ifunc_static.c; perhaps it should be	2022-06-21 16:24:37 +00:00
modules	requires pmap_private.h now.	2022-08-21 14:06:42 +00:00
net	Add test for sys/netipsec/ipsec.c:r1.176.	2022-11-09 08:21:20 +00:00
rump	fix various typos in comments, docs and log messages.	2022-05-24 06:27:59 +00:00
sbin	…
share	…
sys	s/fucntion/function/ in comments.	2022-07-26 19:49:32 +00:00
usr.bin	tests/lint: add more examples for 'extra bits set to 0'	2022-10-15 21:19:15 +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.